summaryrefslogtreecommitdiffstats
path: root/fs/ext3/xattr.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@cse.unsw.edu.au>2005-07-07 17:59:16 -0700
committerLinus Torvalds <torvalds@g5.osdl.org>2005-07-07 18:24:08 -0700
commit375151773125f56b7f6d798d914ea469256b330b (patch)
tree2bc6c0d8d2a075b9daa2aa7dca440f572c566629 /fs/ext3/xattr.c
parent0dd395dc76071a06eea39839cc946c1241af3650 (diff)
downloadop-kernel-dev-375151773125f56b7f6d798d914ea469256b330b.zip
op-kernel-dev-375151773125f56b7f6d798d914ea469256b330b.tar.gz
[PATCH] nfsd4: stop overusing RECLAIM_BAD
A misreading of the spec lead us to convert all errors on open and lock reclaims to RECLAIM_BAD. This causes problems--for example, a reboot within the grace period could lead to reclaims with stale stateid's, and we'd like to return STALE errors in those cases. What rfc3530 actually says about RECLAIM_BAD: "The reclaim provided by the client does not match any of the server's state consistency checks and is bad." I'm assuming that "state consistency checks" refers to checks for consistency with the state recorded to stable storage, and that the error should be reserved for that case. Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/ext3/xattr.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud