nfsd4: return expired on unfound stateid's
authorJ. Bruce Fields <bfields@redhat.com>
Sat, 2 Oct 2010 22:42:39 +0000 (18:42 -0400)
committerJ. Bruce Fields <bfields@redhat.com>
Sat, 2 Oct 2010 22:49:33 +0000 (18:49 -0400)
commit33515142156efc9ab5dbfe93ff8d4765559dc987
tree64dc7ef93b822a703d5ffe32aeb8007550d1daa5
parent328ead287220711c3ad4490b1f3f691855df4039
nfsd4: return expired on unfound stateid's

Commit 78155ed75f470710f2aecb3e75e3d97107ba8374 "nfsd4: distinguish
expired from stale stateids" attempted to distinguish expired and stale
stateid's using time information that may not have been completely
reliable, so I reverted it.

That was throwing out the baby with the bathwater; we still do want to
return expired, but let's do that using the simpler approach of just
assuming any stateid is expired if it looks like it was given out by the
current server instance, but we can't find it any more.

This may help clients that are recovering from network partitions.

Reported-by: Bian Naimeng <biannm@cn.fujitsu.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4state.c