aboutsummaryrefslogtreecommitdiffstats
path: root/fs/nfs
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2013-04-21 18:01:06 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-05-07 19:57:26 -0700
commit3b5f7654971e0dcb6c422d14cbae7309686bb344 (patch)
tree971b0f15ca8856e3464e23f6e6e0b7a2054ef6cc /fs/nfs
parenta35089a9cc44f621e58af899b3483d206bb89284 (diff)
downloadkernel_samsung_smdk4412-3b5f7654971e0dcb6c422d14cbae7309686bb344.tar.gz
kernel_samsung_smdk4412-3b5f7654971e0dcb6c422d14cbae7309686bb344.tar.bz2
kernel_samsung_smdk4412-3b5f7654971e0dcb6c422d14cbae7309686bb344.zip
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/nfs')
0 files changed, 0 insertions, 0 deletions