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:33 -0400 |
commit | ae1007d37e00144b72906a4bdc47d517ae91bcc1 (patch) | |
tree | 170a123bd99aefbb086bef9ab75a576ea5df346a /fs/nfs/nfs4state.c | |
parent | b0ed9dbc24f1fd912b2dd08b995153cafc1d5b1c (diff) | |
download | lwn-ae1007d37e00144b72906a4bdc47d517ae91bcc1.tar.gz lwn-ae1007d37e00144b72906a4bdc47d517ae91bcc1.zip |
NFSv4: Don't call nfs4_state_mark_reclaim_reboot() from error handlers
In the case of a server reboot, the state recovery thread starts by calling
nfs4_state_end_reclaim_reboot() in order to avoid edge conditions when
the server reboots while the client is in the middle of recovery.
However, if the client has already marked the nfs4_state as requiring
reboot recovery, then the above behaviour will cause the recovery thread to
treat the open as if it was part of such an edge condition: the open will
be recovered as if it was part of a lease expiration (and all the locks
will be lost).
Fix is to remove the call to nfs4_state_mark_reclaim_reboot from
nfs4_async_handle_error(), and nfs4_handle_exception(). Instead we leave it
to the recovery thread to do this for us.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: stable@kernel.org
Diffstat (limited to 'fs/nfs/nfs4state.c')
0 files changed, 0 insertions, 0 deletions