diff options
| author | NeilBrown <neilb@suse.de> | 2013-08-12 08:52:47 +0200 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2013-08-22 20:34:14 +0200 |
| commit | 6686390bab6a0e049fa7040631aee08b35a55293 (patch) | |
| tree | de508f578f473a612a2360fa84c98ccd8613364e /fs/nfs/blocklayout | |
| parent | NFSv4.1: Add tracepoints for debugging test_stateid events (diff) | |
| download | linux-6686390bab6a0e049fa7040631aee08b35a55293.tar.xz linux-6686390bab6a0e049fa7040631aee08b35a55293.zip | |
NFS: remove incorrect "Lock reclaim failed!" warning.
After reclaiming state that was lost, the NFS client tries to reclaim
any locks, and then checks that each one has NFS_LOCK_INITIALIZED set
(which means that the server has confirmed the lock).
However if the client holds a delegation, nfs_reclaim_locks() simply aborts
(or more accurately it called nfs_lock_reclaim() and that returns without
doing anything).
This is because when a delegation is held, the server doesn't need to
know about locks.
So if a delegation is held, NFS_LOCK_INITIALIZED is not expected, and
its absence is certainly not an error.
So don't print the warnings if NFS_DELGATED_STATE is set.
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/nfs/blocklayout')
0 files changed, 0 insertions, 0 deletions