1. 07 Jan, 2016 1 commit
    • Kinglong Mee's avatar
      nfsd: Fix nfsd leaks sunrpc module references · 691412b4
      Kinglong Mee authored
      Stefan Hajnoczi reports,
      nfsd leaks 3 references to the sunrpc module here:
      
        # echo -n "asdf 1234" >/proc/fs/nfsd/portlist
        bash: echo: write error: Protocol not supported
      
      Now stop nfsd and try unloading the kernel modules:
      
        # systemctl stop nfs-server
        # systemctl stop nfs
        # systemctl stop proc-fs-nfsd.mount
        # systemctl stop var-lib-nfs-rpc_pipefs.mount
        # rmmod nfsd
        # rmmod nfs_acl
        # rmmod lockd
        # rmmod auth_rpcgss
        # rmmod sunrpc
        rmmod: ERROR: Module sunrpc is in use
        # lsmod | grep rpc
        sunrpc                315392  3
      
      It is caused by nfsd don't cleanup rpcb program for nfsd
      when destroying svc service after creating xprt fail.
      Reported-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      Signed-off-by: default avatarKinglong Mee <kinglongmee@gmail.com>
      Signed-off-by: default avatarJ. Bruce Fields <bfields@redhat.com>
      691412b4
  2. 23 Dec, 2015 1 commit
  3. 10 Aug, 2015 5 commits
  4. 09 Feb, 2015 1 commit
  5. 09 Dec, 2014 1 commit
  6. 01 Aug, 2014 1 commit
  7. 08 Jul, 2014 1 commit
    • Jeff Layton's avatar
      nfsd: add a new /proc/fs/nfsd/max_connections file · 5b8db00b
      Jeff Layton authored
      Currently, the maximum number of connections that nfsd will allow
      is based on the number of threads spawned. While this is fine for a
      default, there really isn't a clear relationship between the two.
      
      The number of threads corresponds to the number of concurrent requests
      that we want to allow the server to process at any given time. The
      connection limit corresponds to the maximum number of clients that we
      want to allow the server to handle. These are two entirely different
      quantities.
      
      Break the dependency on increasing threads in order to allow for more
      connections, by adding a new per-net parameter that can be set to a
      non-zero value. The default is still to base it on the number of threads,
      so there should be no behavior change for anyone who doesn't use it.
      
      Cc: Trond Myklebust <trond.myklebust@primarydata.com>
      Signed-off-by: default avatarJeff Layton <jlayton@primarydata.com>
      Signed-off-by: default avatarJ. Bruce Fields <bfields@redhat.com>
      5b8db00b
  8. 23 Jun, 2014 1 commit
  9. 22 May, 2014 1 commit
    • NeilBrown's avatar
      nfsd: Only set PF_LESS_THROTTLE when really needed. · 8658452e
      NeilBrown authored
      PF_LESS_THROTTLE has a very specific use case: to avoid deadlocks
      and live-locks while writing to the page cache in a loop-back
      NFS mount situation.
      
      It therefore makes sense to *only* set PF_LESS_THROTTLE in this
      situation.
      We now know when a request came from the local-host so it could be a
      loop-back mount.  We already know when we are handling write requests,
      and when we are doing anything else.
      
      So combine those two to allow nfsd to still be throttled (like any
      other process) in every situation except when it is known to be
      problematic.
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      Signed-off-by: default avatarJ. Bruce Fields <bfields@redhat.com>
      8658452e
  10. 06 Jan, 2014 1 commit
  11. 03 Jan, 2014 1 commit
  12. 12 Jul, 2013 1 commit
    • J. Bruce Fields's avatar
      nfsd4: fix minorversion support interface · 35f7a14f
      J. Bruce Fields authored
      You can turn on or off support for minorversions using e.g.
      
      	echo "-4.2" >/proc/fs/nfsd/versions
      
      However, the current implementation is a little wonky.  For example, the
      above will turn off 4.2 support, but it will also turn *on* 4.1 support.
      
      This didn't matter as long as we only had 2 minorversions, which was
      true till very recently.
      
      And do a little cleanup here.
      Signed-off-by: default avatarJ. Bruce Fields <bfields@redhat.com>
      35f7a14f
  13. 08 Jul, 2013 1 commit
  14. 23 Feb, 2013 1 commit
  15. 15 Feb, 2013 1 commit
    • Stanislav Kinsbursky's avatar
      nfsd: containerize NFSd filesystem · 11f77942
      Stanislav Kinsbursky authored
      This patch makes NFSD file system superblock to be created per net.
      This makes possible to get proper network namespace from superblock instead of
      using hard-coded "init_net".
      
      Note: NFSd fs super-block holds network namespace. This garantees, that
      network namespace won't disappear from underneath of it.
      This, obviously, means, that in case of kill of a container's "init" (which is not a mount
      namespace, but network namespace creator) netowrk namespace won't be
      destroyed.
      Signed-off-by: default avatarStanislav Kinsbursky <skinsbursky@parallels.com>
      Signed-off-by: default avatarJ. Bruce Fields <bfields@redhat.com>
      11f77942
  16. 04 Feb, 2013 1 commit
  17. 10 Dec, 2012 15 commits
  18. 28 Nov, 2012 1 commit
  19. 26 Nov, 2012 1 commit
  20. 21 Aug, 2012 2 commits
  21. 25 Jul, 2012 1 commit