diff options
author | Alexander Aring <aahringo@redhat.com> | 2023-05-29 17:44:29 -0400 |
---|---|---|
committer | David Teigland <teigland@redhat.com> | 2023-06-14 10:17:33 -0500 |
commit | c6b6d6dcc7f32767d57740e0552337c8de40610b (patch) | |
tree | 20acbdc646de907a8c6dd67f79a88ea90b8d19a9 /io_uring/uring_cmd.c | |
parent | 57e2c2f2d94cfd551af91cedfa1af6d972487197 (diff) |
fs: dlm: revert check required context while close
This patch reverts commit 2c3fa6ae4d52 ("dlm: check required context
while close"). The function dlm_midcomms_close(), which will call later
dlm_lowcomms_close(), is called when the cluster manager tells the node
got fenced which means on midcomms/lowcomms layer to disconnect the node
from the cluster communication. The node can rejoin the cluster later.
This patch was ensuring no new message were able to be triggered when we
are in the close() function context. This was done by checking if the
lockspace has been stopped. However there is a missing check that we
only need to check specific lockspaces where the fenced node is member
of. This is currently complicated because there is no way to easily
check if a node is part of a specific lockspace without stopping the
recovery. For now we just revert this commit as it is just a check to
finding possible leaks of stopping lockspaces before close() is called.
Cc: stable@vger.kernel.org
Fixes: 2c3fa6ae4d52 ("dlm: check required context while close")
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'io_uring/uring_cmd.c')
0 files changed, 0 insertions, 0 deletions