1. 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
  2. 10 7月, 2008 2 次提交
  3. 19 5月, 2008 5 次提交
  4. 24 4月, 2008 6 次提交
  5. 20 4月, 2008 4 次提交
    • T
      SUNRPC: Don't disconnect more than once if retransmitting NFSv4 requests · 7c1d71cf
      Trond Myklebust 提交于
      NFSv4 requires us to ensure that we break the TCP connection before we're
      allowed to retransmit a request. However in the case where we're
      retransmitting several requests that have been sent on the same
      connection, we need to ensure that we don't interfere with the attempt to
      reconnect and/or break the connection again once it has been established.
      
      We therefore introduce a 'connection' cookie that is bumped every time a
      connection is broken. This allows requests to track if they need to force a
      disconnection.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      7c1d71cf
    • T
      NFSv4: Reintroduce machine creds · 7c67db3a
      Trond Myklebust 提交于
      We need to try to ensure that we always use the same credentials whenever
      we re-establish the clientid on the server. If not, the server won't
      recognise that we're the same client, and so may not allow us to recover
      state.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      7c67db3a
    • T
      NFSv4: Don't use cred->cr_ops->cr_name in nfs4_proc_setclientid() · 78ea323b
      Trond Myklebust 提交于
      With the recent change to generic creds, we can no longer use
      cred->cr_ops->cr_name to distinguish between RPCSEC_GSS principals and
      AUTH_SYS/AUTH_NULL identities. Replace it with the rpc_authops->au_name
      instead...
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      78ea323b
    • T
      SUNRPC: Fix up xprt_write_space() · b6ddf64f
      Trond Myklebust 提交于
      The rest of the networking layer uses SOCK_ASYNC_NOSPACE to signal whether
      or not we have someone waiting for buffer memory. Convert the SUNRPC layer
      to use the same idiom.
      Remove the unlikely()s in xs_udp_write_space and xs_tcp_write_space. In
      fact, the most common case will be that there is nobody waiting for buffer
      space.
      
      SOCK_NOSPACE is there to tell the TCP layer whether or not the cwnd was
      limited by the application window. Ensure that we follow the same idiom as
      the rest of the networking layer here too.
      
      Finally, ensure that we clear SOCK_ASYNC_NOSPACE once we wake up, so that
      write_space() doesn't keep waking things up on xprt->pending.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      b6ddf64f
  6. 15 3月, 2008 5 次提交
  7. 29 2月, 2008 5 次提交
  8. 26 2月, 2008 4 次提交
  9. 15 2月, 2008 1 次提交
  10. 11 2月, 2008 1 次提交
    • J
      nfsd: clean up svc_reserve_auth() · fbb7878c
      J. Bruce Fields 提交于
      This is a void function attempting to return the return value from
      another void function, which seems harmless but extremely weird, and
      apparently makes some compilers complain.
      
      While we're there, clean up a little (e.g. the switch statement had a
      minor style problem and seemed overkill as long as there's only one
      case).
      
      Thanks to Trond for noticing this.
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      Cc: Trond Myklebust <Trond.Myklebust@netapp.com>
      fbb7878c
  11. 02 2月, 2008 6 次提交