Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
大约 1 年 前同步成功

通知 153
Star 36
Fork 7
cloud-kernel
cloud-kernel

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 24 10月, 2011 2 次提交
  3. 19 10月, 2011 1 次提交
  5. 17 10月, 2011 1 次提交
  7. 12 10月, 2011 1 次提交
  9. 11 10月, 2011 1 次提交
  11. 27 9月, 2011 2 次提交
    • J
      nfsd4: look up stateid's per clientid · 38c2f4b1
      由 J. Bruce Fields 提交于 
      Use a separate stateid idr per client, and lookup a stateid by first
finding the client, then looking up the stateid relative to that client.

Also some minor refactoring.

This allows us to improve error returns: we can return expired when the
clientid is not found and bad_stateid when the clientid is found but not
the stateid, as opposed to returning expired for both cases.

I hope this will also help to replace the state lock mostly by a
per-client lock, but that hasn't been done yet.
Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      38c2f4b1
    • J
      nfsd4: assume test_stateid always has session · 36279ac1
      由 J. Bruce Fields 提交于 
      Test_stateid is 4.1-only and only allowed after a sequence operation, so
this check is unnecessary.

Cc: Bryan Schumaker <bjschuma@netapp.com>
Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      36279ac1
  13. 17 9月, 2011 1 次提交
  15. 16 9月, 2011 1 次提交
    • M
      nfsd41: try to check reply size before operation · 58e7b33a
      由 Mi Jinlong 提交于 
      For checking the size of reply before calling a operation,
we need try to get maxsize of the operation's reply.

v3: using new method as Bruce said,

 "we could handle operations in two different ways:

	- For operations that actually change something (write, rename,
	  open, close, ...), do it the way we're doing it now: be
	  very careful to estimate the size of the response before even
	  processing the operation.
	- For operations that don't change anything (read, getattr, ...)
	  just go ahead and do the operation.  If you realize after the
	  fact that the response is too large, then return the error at
	  that point.

  So we'd add another flag to op_flags: say, OP_MODIFIES_SOMETHING.  And for
  operations with OP_MODIFIES_SOMETHING set, we'd do the first thing.  For
  operations without it set, we'd do the second."
Signed-off-by: NMi Jinlong <mijinlong@cn.fujitsu.com>
[bfields@redhat.com: crash, don't attempt to handle, undefined op_rsize_bop]
Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      58e7b33a
  17. 14 9月, 2011 1 次提交
  19. 07 9月, 2011 1 次提交
  21. 01 9月, 2011 4 次提交
  23. 28 8月, 2011 1 次提交
  25. 27 8月, 2011 2 次提交
    • J
      nfsd4: it's OK to return nfserr_symlink · 75c096f7
      由 J. Bruce Fields 提交于 
      The nfsd4 code has a bunch of special exceptions for error returns which
map nfserr_symlink to other errors.

In fact, the spec makes it clear that nfserr_symlink is to be preferred
over less specific errors where possible.

The patch that introduced it back in 2.6.4 is "kNFSd: correct symlink
related error returns.", which claims that these special exceptions are
represent an NFSv4 break from v2/v3 tradition--when in fact the symlink
error was introduced with v4.

I suspect what happened was pynfs tests were written that were overly
faithful to the (known-incomplete) rfc3530 error return lists, and then
code was fixed up mindlessly to make the tests pass.

Delete these unnecessary exceptions.
Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      75c096f7
    • J
      nfsd4: clean up S_IS -> NF4 file type mapping · 3d2544b1
      由 J. Bruce Fields 提交于 
      A slightly unconventional approach to make the code more compact I could
live with, but let's give the poor reader *some* chance.
Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      3d2544b1
  27. 20 8月, 2011 1 次提交
  29. 18 7月, 2011 2 次提交
  31. 16 7月, 2011 2 次提交
  33. 19 5月, 2011 1 次提交
  35. 30 4月, 2011 2 次提交
  37. 18 3月, 2011 1 次提交
  39. 09 3月, 2011 1 次提交
  41. 17 2月, 2011 1 次提交
  43. 12 1月, 2011 2 次提交
  45. 05 1月, 2011 3 次提交
  47. 30 12月, 2010 1 次提交
  49. 18 12月, 2010 1 次提交
  51. 20 11月, 2010 1 次提交
  53. 02 10月, 2010 1 次提交
  55. 10 8月, 2010 1 次提交
    • C
      pass a struct path to vfs_statfs · ebabe9a9
      由 Christoph Hellwig 提交于 
      We'll need the path to implement the flags field for statvfs support.
We do have it available in all callers except:

 - ecryptfs_statfs.  This one doesn't actually need vfs_statfs but just
   needs to do a caller to the lower filesystem statfs method.
 - sys_ustat.  Add a non-exported statfs_by_dentry helper for it which
   doesn't won't be able to fill out the flags field later on.

In addition rename the helpers for statfs vs fstatfs to do_*statfs instead
of the misleading vfs prefix.
Signed-off-by: NChristoph Hellwig <hch@lst.de>
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      ebabe9a9