diff options
author | NeilBrown | 2022-10-10 10:26:51 +1100 |
---|---|---|
committer | Trond Myklebust | 2022-12-06 10:45:11 -0500 |
commit | ef8d98f20dfc79777d2b66a30926533225dc6efa (patch) | |
tree | 045d63568aabe0c9fb21918cbbe22035fe870fde /net/sunrpc | |
parent | 5559405df652008e56eee88872126fe4c451da67 (diff) |
NFS: avoid spurious warning of lost lock that is being unlocked.
When the NFSv4 state manager recovers state after a server restart, it
reports that locks have been lost if it finds any lock state for which
recovery hasn't been successful. i.e. any for which
NFS_LOCK_INITIALIZED is not set.
However it only tries to recover locks that are still linked to
inode->i_flctx. So if a lock has been removed from inode->i_flctx, but
the state for that lock has not yet been destroyed, then a spurious
warning results.
nfs4_proc_unlck() calls locks_lock_inode_wait() - which removes the lock
from ->i_flctx - before sending the unlock request to the server and
before the final nfs4_put_lock_state() is called. This allows a window
in which a spurious warning can be produced.
So add a new flag NFS_LOCK_UNLOCKING which is set once the decision has
been made to unlock the lock. This will prevent it from triggering any
warning.
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Diffstat (limited to 'net/sunrpc')
0 files changed, 0 insertions, 0 deletions