NFSv4: nfs4_stateid_is_current should return 'true' for an invalid stateid
authorTrond Myklebust <trond.myklebust@primarydata.com>
Wed, 5 Mar 2014 13:44:23 +0000 (08:44 -0500)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Wed, 5 Mar 2014 16:55:06 +0000 (11:55 -0500)
commite1253be0ece1a95a02c7f5843194877471af8179
treed5f22de8fec53058a624f308df1375973c264c79
parent755a48a7a4eb05b9c8424e3017d947b2961a60e0
NFSv4: nfs4_stateid_is_current should return 'true' for an invalid stateid

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
Cc: stable@vger.kernel.org # 3.10+
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
fs/nfs/nfs4proc.c