diff options
| author | NeilBrown <[email protected]> | 2005-07-08 00:59:16 +0000 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2005-07-08 01:24:08 +0000 |
| commit | 375151773125f56b7f6d798d914ea469256b330b (patch) | |
| tree | 2bc6c0d8d2a075b9daa2aa7dca440f572c566629 /net/unix/af_unix.c | |
| parent | [PATCH] nfsd4: ERR_GRACE should bump seqid on lock (diff) | |
| download | kernel-375151773125f56b7f6d798d914ea469256b330b.tar.gz kernel-375151773125f56b7f6d798d914ea469256b330b.zip | |
[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 <[email protected]>
Signed-off-by: Neil Brown <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions