diff options
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2010-10-04 17:59:08 -0400 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2010-10-19 19:42:53 -0400 |
| commit | 6eaa61496fb3b93cceface7a296415fc4c030bce (patch) | |
| tree | 88093c8ca07058b940a871d92fd1074968098dbe /fs/ext3 | |
| parent | ae1007d37e00144b72906a4bdc47d517ae91bcc1 (diff) | |
| download | blackbird-op-linux-6eaa61496fb3b93cceface7a296415fc4c030bce.tar.gz blackbird-op-linux-6eaa61496fb3b93cceface7a296415fc4c030bce.zip | |
NFSv4: Don't call nfs4_reclaim_complete() on receiving NFS4ERR_STALE_CLIENTID
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>
Cc: stable@kernel.org
Diffstat (limited to 'fs/ext3')
0 files changed, 0 insertions, 0 deletions
