diff options
author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2013-04-21 18:01:06 -0400 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-05-07 20:33:12 -0700 |
commit | 17f978ddc76d3163bc4dd2d6bf7dd848065b4c78 (patch) | |
tree | 689b7eef91cdff1b8b9f87bdab264e46bcbb2c3f /fs/dlm | |
parent | 0565d71131f1e4d6a7d3eaf338dab5431a4fbc81 (diff) |
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>
Diffstat (limited to 'fs/dlm')
0 files changed, 0 insertions, 0 deletions