1. 17 12月, 2010 2 次提交
  2. 02 10月, 2010 1 次提交
  3. 17 9月, 2010 1 次提交
  4. 13 9月, 2010 1 次提交
  5. 04 8月, 2010 2 次提交
  6. 14 9月, 2009 1 次提交
  7. 21 8月, 2009 3 次提交
  8. 10 8月, 2009 3 次提交
    • T
      SUNRPC: clean up rpc_setup_pipedir() · 23ac6581
      Trond Myklebust 提交于
      There is still a little wart or two there: Since we've already got a
      vfsmount, we might as well pass that in to rpc_create_client_dir.
      Another point is that if we open code __rpc_lookup_path() here, then we can
      avoid looking up the entire parent directory path over and over again: it
      doesn't change.
      
      Also get rid of rpc_clnt->cl_pathname, since it has no users...
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      23ac6581
    • T
    • C
      SUNRPC: Provide functions for managing universal addresses · a02d6926
      Chuck Lever 提交于
      Introduce a set of functions in the kernel's RPC implementation for
      converting between a socket address and either a standard
      presentation address string or an RPC universal address.
      
      The universal address functions will be used to encode and decode
      RPCB_FOO and NFSv4 SETCLIENTID arguments.  The other functions are
      part of a previous promise to deliver shared functions that can be
      used by upper-layer protocols to display and manipulate IP
      addresses.
      
      The kernel's current address printf formatters were designed
      specifically for kernel to user-space APIs that require a particular
      string format for socket addresses, thus are somewhat limited for the
      purposes of sunrpc.ko.  The formatter for IPv6 addresses, %pI6, does
      not support short-handing or scope IDs.  Also, these printf formatters
      are unique per address family, so a separate formatter string is
      required for printing AF_INET and AF_INET6 addresses.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      a02d6926
  9. 18 6月, 2009 1 次提交
  10. 24 12月, 2008 1 次提交
  11. 30 9月, 2008 2 次提交
    • B
      nfsd: use nfs client rpc callback program · d5b337b4
      Benny Halevy 提交于
      since commit ff7d9756
      "nfsd: use static memory for callback program and stats"
      do_probe_callback uses a static callback program
      (NFS4_CALLBACK) rather than the one set in clp->cl_callback.cb_prog
      as passed in by the client in setclientid (4.0)
      or create_session (4.1).
      
      This patches introduces rpc_create_args.prognumber that allows
      overriding program->number when creating rpc_clnt.
      Signed-off-by: NBenny Halevy <bhalevy@panasas.com>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      d5b337b4
    • C
      SUNRPC: Simplify rpcb_register() API · 14aeb211
      Chuck Lever 提交于
      Bruce suggested there's no need to expose the difference between an error
      sending the PMAP_SET request and an error reply from the portmapper to
      rpcb_register's callers.  The user space equivalent of rpcb_register() is
      pmap_set(3), which returns a bool_t : either the PMAP set worked, or it
      didn't.  Simple.
      
      So let's remove the "*okay" argument from rpcb_register() and
      rpcb_v4_register(), and simply return an error if any part of the call
      didn't work.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      14aeb211
  12. 16 7月, 2008 1 次提交
    • C
      SUNRPC: Support registering IPv6 interfaces with local rpcbind daemon · c2e1b09f
      Chuck Lever 提交于
      Introduce a new API to register RPC services on IPv6 interfaces to allow
      the NFS server and lockd to advertise on IPv6 networks.
      
      Unlike rpcb_register(), the new rpcb_v4_register() function uses rpcbind
      protocol version 4 to contact the local rpcbind daemon.  The version 4
      SET/UNSET procedures allow services to register address families besides
      AF_INET, register at specific network interfaces, and register transport
      protocols besides UDP and TCP.  All of this functionality is exposed via
      the new rpcb_v4_register() kernel API.
      
      A user-space rpcbind daemon implementation that supports version 4 of the
      rpcbind protocol is required in order to make use of this new API.
      
      Note that rpcbind version 3 is sufficient to support the new rpcbind
      facilities listed above, but most extant implementations use version 4.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      c2e1b09f
  13. 10 7月, 2008 1 次提交
    • O
      rpc: bring back cl_chatty · b6b6152c
      Olga Kornievskaia 提交于
      The cl_chatty flag alows us to control whether a given rpc client leaves
      
      	"server X not responding, timed out"
      
      messages in the syslog.  Such messages make sense for ordinary nfs
      clients (where an unresponsive server means applications on the
      mountpoint are probably hanging), but not for the callback client (which
      can fail more commonly, with the only result just of disabling some
      optimizations).
      
      Previously cl_chatty was removed, do to lack of users; reinstate it, and
      use it for the nfsd's callback client.
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      b6b6152c
  14. 15 2月, 2008 1 次提交
  15. 30 1月, 2008 6 次提交
  16. 07 12月, 2007 1 次提交
  17. 10 10月, 2007 1 次提交
  18. 11 7月, 2007 11 次提交