1. 05 12月, 2009 3 次提交
  2. 04 12月, 2009 3 次提交
  3. 11 11月, 2009 1 次提交
  4. 26 10月, 2009 1 次提交
  5. 24 10月, 2009 1 次提交
    • T
      NFSv4: Fix a bug when the server returns NFS4ERR_RESOURCE · 52567b03
      Trond Myklebust 提交于
      RFC 3530 states that when we recieve the error NFS4ERR_RESOURCE, we are not
      supposed to bump the sequence number on OPEN, LOCK, LOCKU, CLOSE, etc
      operations. The problem is that we map that error into EREMOTEIO in the XDR
      layer, and so the NFSv4 middle-layer routines like seqid_mutating_err(),
      and nfs_increment_seqid() don't recognise it.
      
      The fix is to defer the mapping until after the middle layers have
      processed the error.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      52567b03
  6. 24 9月, 2009 1 次提交
  7. 10 8月, 2009 2 次提交
  8. 22 7月, 2009 2 次提交
    • T
      NFSv4: Fix a problem whereby a buggy server can oops the kernel · d953126a
      Trond Myklebust 提交于
      We just had a case in which a buggy server occasionally returns the wrong
      attributes during an OPEN call. While the client does catch this sort of
      condition in nfs4_open_done(), and causes the nfs4_atomic_open() to return
      -EISDIR, the logic in nfs_atomic_lookup() is broken, since it causes a
      fallback to an ordinary lookup instead of just returning the error.
      
      When the buggy server then returns a regular file for the fallback lookup,
      the VFS allows the open, and bad things start to happen, since the open
      file doesn't have any associated NFSv4 state.
      
      The fix is firstly to return the EISDIR/ENOTDIR errors immediately, and
      secondly to ensure that we are always careful when dereferencing the
      nfs_open_context state pointer.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      d953126a
    • T
      NFSv4: Fix an NFSv4 mount regression · fccba804
      Trond Myklebust 提交于
      Commit 008f55d0 (nfs41: recover lease in
      _nfs4_lookup_root) forces the state manager to always run on mount. This is
      a bug in the case of NFSv4.0, which doesn't require us to send a
      setclientid until we want to grab file state.
      
      In any case, this is completely the wrong place to be doing state
      management. Moving that code into nfs4_init_session...
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      fccba804
  9. 13 7月, 2009 1 次提交
  10. 21 6月, 2009 1 次提交
  11. 18 6月, 2009 24 次提交