1. 06 11月, 2006 1 次提交
  2. 21 10月, 2006 2 次提交
  3. 17 10月, 2006 2 次提交
    • N
      [PATCH] knfsd: Allow lockd to drop replies as appropriate · d343fce1
      NeilBrown 提交于
      It is possible for the ->fopen callback from lockd into nfsd to find that an
      answer cannot be given straight away (an upcall is needed) and so the request
      has to be 'dropped', to be retried later.  That error status is not currently
      propagated back.
      
      So:
        Change nlm_fopen to return nlm error codes (rather than a private
        protocol) and define a new nlm_drop_reply code.
        Cause nlm_drop_reply to cause the rpc request to get rpc_drop_reply
        when this error comes back.
        Cause svc_process to drop a request which returns a status of
        rpc_drop_reply.
      
      [akpm@osdl.org: fix warning storm]
      Cc: Marc Eshel <eshel@almaden.ibm.com>
      Signed-off-by: NNeil Brown <neilb@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      d343fce1
    • N
      [PATCH] knfsd: Fix bug in recent lockd patches that can cause reclaim to fail · 4481d103
      NeilBrown 提交于
      When an nfs server shuts down, lockd needs to release all the locks even
      though the client still holds them.
      
      It should therefore not 'unmonitor' the clients, so that the files in nfs/sm
      will still be there when the nfs server restarts, so that those clients will
      be told to reclaim their locks.
      
      However the hosts are fully unmonitored, so statd may well remove the files.
      
      lockd has a test for 'sm_sticky' and avoid the unmonitor call if it is set,
      but it is currently not set.
      
      So set it when tearing down lockd.
      Signed-off-by: NNeil Brown <neilb@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4481d103
  4. 04 10月, 2006 20 次提交
  5. 02 10月, 2006 6 次提交
  6. 27 9月, 2006 3 次提交
  7. 23 9月, 2006 3 次提交
  8. 25 8月, 2006 1 次提交
  9. 04 8月, 2006 1 次提交
  10. 06 7月, 2006 1 次提交