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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 8 May 2013 02:51:56 +0000 (19:51 -0700)
commit02d1a16d6d89faa6f78625ea17be9f0b995e44ab
tree0f03a668a0343c8fe4b36685e10c0281afe67d7a
parentb51c8db5eb83b14921e6017aa9c67b82f80260b1
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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/lockd/clntlock.c
fs/lockd/clntproc.c