]> git.karo-electronics.de Git - karo-tx-linux.git/commit
NFSv4: Don't call nfs4_reclaim_complete() on receiving NFS4ERR_STALE_CLIENTID
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Mon, 4 Oct 2010 21:59:08 +0000 (17:59 -0400)
committerGreg Kroah-Hartman <gregkh@suse.de>
Thu, 9 Dec 2010 21:32:20 +0000 (13:32 -0800)
commit4e16957a4c2b79a4bfb9b294e6060cbc257dd094
tree5e29e79bf08ca41c479f736d0853e027bae7c34c
parentb699221e9f33d24d80dc11206315697cda354c78
NFSv4: Don't call nfs4_reclaim_complete() on receiving NFS4ERR_STALE_CLIENTID

commit 6eaa61496fb3b93cceface7a296415fc4c030bce upstream.

If the server sends us an NFS4ERR_STALE_CLIENTID while the state management
thread is busy reclaiming state, we do want to treat all state that wasn't
reclaimed before the STALE_CLIENTID as if a network partition occurred (see
the edge conditions described in RFC3530 and RFC5661).
What we do not want to do is to send an nfs4_reclaim_complete(), since we
haven't yet even started reclaiming state after the server rebooted.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
fs/nfs/nfs4state.c