[PATCH 0/1] NFSv4.0 reclaim reboot state when re-establishing clientid

[andros@netapp.com]

From: Andy Adamson <andros@netapp.com>

This patch fixes an infinite loop where a file is open during a reboot, and 
written to after the reboot. NFS4ERR_BADSESSION is intially returned, and
first the session, and then the clientid are re-established.  But since the
open state was not recovered, the write after reboot would use the old stateid.
The server then returns NFS4ERR_STALE_STATEID as it should, and the client
then goes into the NFS4CLNT_CHECK_LEASE state which sends a solo sequence
operation to check the lease. Since the clientid/session has been
re-established, the NFS4CLNT_CHECK_LEASE does not receive an error, and the
write is resent with the old stateid.....


-->Andy

Andy Adamson (1):
  NFSv4.0 reclaim reboot state when re-establishing clientid

 fs/nfs/nfs4state.c |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

-- 
1.7.7.6