summaryrefslogtreecommitdiffstats
path: root/lib/lcm.c
diff options
context:
space:
mode:
authorChangwei Ge <gechangwei@live.cn>2019-09-23 15:33:37 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-10-07 21:01:03 +0200
commit68fb386f396a1d48847b9afd5b936016ee797c3c (patch)
tree1bded1f9d50c3814639e71b6b23eafd9e5afa75b /lib/lcm.c
parentfe276165b08188616fca013b3df0f7373e8d51dd (diff)
downloadlinux-stable-68fb386f396a1d48847b9afd5b936016ee797c3c.tar.gz
linux-stable-68fb386f396a1d48847b9afd5b936016ee797c3c.tar.bz2
linux-stable-68fb386f396a1d48847b9afd5b936016ee797c3c.zip
ocfs2: wait for recovering done after direct unlock request
[ Upstream commit 0a3775e4f883912944481cf2ef36eb6383a9cc74 ] There is a scenario causing ocfs2 umount hang when multiple hosts are rebooting at the same time. NODE1 NODE2 NODE3 send unlock requset to NODE2 dies become recovery master recover NODE2 find NODE2 dead mark resource RECOVERING directly remove lock from grant list calculate usage but RECOVERING marked **miss the window of purging clear RECOVERING To reproduce this issue, crash a host and then umount ocfs2 from another node. To solve this, just let unlock progress wait for recovery done. Link: http://lkml.kernel.org/r/1550124866-20367-1-git-send-email-gechangwei@live.cn Signed-off-by: Changwei Ge <gechangwei@live.cn> Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com> Cc: Mark Fasheh <mark@fasheh.com> Cc: Joel Becker <jlbec@evilplan.org> Cc: Junxiao Bi <junxiao.bi@oracle.com> Cc: Changwei Ge <gechangwei@live.cn> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'lib/lcm.c')
0 files changed, 0 insertions, 0 deletions