1. 11 4月, 2013 2 次提交
  2. 09 4月, 2013 3 次提交
  3. 06 4月, 2013 11 次提交
  4. 29 3月, 2013 2 次提交
    • T
      NFSv4: Fix Oopses in the fs_locations code · 809b426c
      Trond Myklebust 提交于
      If the server sends us a pathname with more components than the client
      limit of NFS4_PATHNAME_MAXCOMPONENTS, more server entries than the client
      limit of NFS4_FS_LOCATION_MAXSERVERS, or sends a total number of
      fs_locations entries than the client limit of NFS4_FS_LOCATIONS_MAXENTRIES
      then we will currently Oops because the limit checks are done _after_ we've
      decoded the data into the arrays.
      
      Reported-by: fanchaoting<fanchaoting@cn.fujitsu.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      809b426c
    • T
      NFSv4: Fix another reboot recovery race · 91876b13
      Trond Myklebust 提交于
      If the open_context for the file is not yet fully initialised,
      then open recovery cannot succeed, and since nfs4_state_find_open_context
      returns an ENOENT, we end up treating the file as being irrecoverable.
      
      What we really want to do, is just defer the recovery until later.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      91876b13
  5. 28 3月, 2013 1 次提交
  6. 26 3月, 2013 12 次提交
  7. 25 3月, 2013 1 次提交
  8. 21 3月, 2013 5 次提交
  9. 04 3月, 2013 3 次提交