NFS: remove incorrect "Lock reclaim failed!" warning.
authorNeilBrown <neilb@suse.de>
Mon, 12 Aug 2013 06:52:47 +0000 (16:52 +1000)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Thu, 22 Aug 2013 18:34:14 +0000 (14:34 -0400)
commit6686390bab6a0e049fa7040631aee08b35a55293
treede508f578f473a612a2360fa84c98ccd8613364e
parent08cb47faa4687342e9cbde54ff0f15a768eb5632
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>
fs/nfs/nfs4state.c