LOCKD: Ensure that nlmclnt_block resets block->b_status after a server reboot
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Sun, 21 Apr 2013 22:01:06 +0000 (18:01 -0400)
committerBen Hutchings <ben@decadent.org.uk>
Mon, 13 May 2013 14:02:22 +0000 (15:02 +0100)
commit7d803dc3d974ba8e9e7781b30079d8dc7640e1f7
tree7614a3aa91278de8b5ad625319f86ae226b9bacb
parentfcf565be6168313624ac7c0d34d64c92fc967a81
LOCKD: Ensure that nlmclnt_block resets block->b_status after a server reboot

commit 1dfd89af8697a299e7982ae740d4695ecd917eef upstream.

After a server reboot, the reclaimer thread will recover all the existing
locks. For locks that are blocked, however, it will change the value
of block->b_status to nlm_lck_denied_grace_period in order to signal that
they need to wake up and resend the original blocking lock request.

Due to a bug, however, the block->b_status never gets reset after the
blocked locks have been woken up, and so the process goes into an
infinite loop of resends until the blocked lock is satisfied.

Reported-by: Marc Eshel <eshel@us.ibm.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
fs/lockd/clntlock.c
fs/lockd/clntproc.c