1. 24 12月, 2008 2 次提交
    • J
      sunrpc: fix code that makes auth_gss send destroy_cred message (try #2) · 6dcd3926
      Jeff Layton 提交于
      There's a bit of a chicken and egg problem when it comes to destroying
      auth_gss credentials. When we destroy the last instance of a GSSAPI RPC
      credential, we should send a NULL RPC call with a GSS procedure of
      RPCSEC_GSS_DESTROY to hint to the server that it can destroy those
      creds.
      
      This isn't happening because we're setting clearing the uptodate bit on
      the credentials and then setting the operations to the gss_nullops. When
      we go to do the RPC call, we try to refresh the creds. That fails with
      -EACCES and the call fails.
      
      Fix this by not clearing the UPTODATE bit for the credentials and adding
      a new crdestroy op for gss_nullops that just tears down the cred without
      trying to destroy the context.
      
      The only difference between this patch and the first one is the removal
      of some minor formatting deltas.
      Signed-off-by: NJeff Layton <jlayton@redhat.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      6dcd3926
    • T
      SUNRPC: Remove the last remnant of the BKL... · 88a9fe8c
      Trond Myklebust 提交于
      Somehow, this escaped the previous purge. There should be no need to keep
      any extra locks in the XDR callbacks.
      
      The NFS client XDR code only writes into private objects, whereas all reads
      of shared objects are confined to fields that do not change, such as
      filehandles...
      
      Ditto for lockd, the NFSv2/v3 client mount code, and rpcbind.
      
      The nfsd XDR code may require the BKL, but since it does a synchronous RPC
      call from a thread that already holds the lock, that issue is moot.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      88a9fe8c
  2. 10 7月, 2008 3 次提交
  3. 12 6月, 2008 1 次提交
  4. 20 4月, 2008 5 次提交
  5. 15 3月, 2008 1 次提交
  6. 06 3月, 2008 1 次提交
  7. 29 2月, 2008 1 次提交
  8. 26 2月, 2008 1 次提交
    • T
      SUNRPC: Run rpc timeout functions as callbacks instead of in softirqs · 5d00837b
      Trond Myklebust 提交于
      An audit of the current RPC timeout functions shows that they don't really
      ever need to run in the softirq context. As long as the softirq is
      able to signal that the wakeup is due to a timeout (which it can do by
      setting task->tk_status to -ETIMEDOUT) then the callback functions can just
      run as standard task->tk_callback functions (in the rpciod/process
      context).
      
      The only possible border-line case would be xprt_timer() for the case of
      UDP, when the callback is used to reduce the size of the transport
      congestion window. In testing, however, the effect of moving that update
      to a callback would appear to be minor.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      5d00837b
  9. 30 1月, 2008 1 次提交
  10. 03 1月, 2008 1 次提交
  11. 27 11月, 2007 1 次提交
  12. 20 11月, 2007 1 次提交
  13. 18 11月, 2007 1 次提交
  14. 08 8月, 2007 1 次提交
  15. 20 7月, 2007 1 次提交
  16. 17 7月, 2007 1 次提交
  17. 11 7月, 2007 16 次提交
  18. 11 2月, 2007 1 次提交