diff options
| author | Trond Myklebust <trond.myklebust@primarydata.com> | 2014-03-05 08:44:23 -0500 |
|---|---|---|
| committer | Jiri Slaby <jslaby@suse.cz> | 2014-03-22 22:01:58 +0100 |
| commit | ff3918ebdc2d35c0e57b6aa8c32098f40ab83bd0 (patch) | |
| tree | a2f02bc38616e17764933a299275b32e0050f667 /fs/afs/afs_fs.h | |
| parent | 793c6f9509f87e2918a551e88605d833cacc9546 (diff) | |
NFSv4: nfs4_stateid_is_current should return 'true' for an invalid stateid
commit e1253be0ece1a95a02c7f5843194877471af8179 upstream.
When nfs4_set_rw_stateid() can fails by returning EIO to indicate that
the stateid is completely invalid, then it makes no sense to have it
trigger a retry of the READ or WRITE operation. Instead, we should just
have it fall through and attempt a recovery.
This fixes an infinite loop in which the client keeps replaying the same
bad stateid back to the server.
Reported-by: Andy Adamson <andros@netapp.com>
Link: http://lkml.kernel.org/r/1393954269-3974-1-git-send-email-andros@netapp.com
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Diffstat (limited to 'fs/afs/afs_fs.h')
0 files changed, 0 insertions, 0 deletions