cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
* [Cluster-devel] [GFS2 PATCH] gfs2: Fix regression in freeze_go_sync
       [not found] <796995883.26198021.1605642034293.JavaMail.zimbra@redhat.com>
@ 2020-11-17 19:40 ` Bob Peterson
  0 siblings, 0 replies; only message in thread
From: Bob Peterson @ 2020-11-17 19:40 UTC (permalink / raw)
  To: cluster-devel.redhat.com

Hi,

Patch 541656d3a51 ("gfs2: freeze should work on read-only mounts") changed the
check for glock state in function freeze_go_sync() from "gl->gl_state ==
LM_ST_SHARED" to "gl->gl_req == LM_ST_EXCLUSIVE". That's wrong and it regressed
gfs2's freeze/thaw mechanism.

We need to check gl_state == LM_ST_SHARED and not gl_req == LM_ST_EXCLUSIVE
because when any node does a freeze, all the nodes should have the freeze glock
in SH mode and they all call do_xmote: One node for EX and the others for UN.
They ALL must freeze locally, and they ALL must queue freeze work. The
freeze_work calls freeze_func, which reacquires the freeze glock in SH,
effectively waiting for the thaw on the node who holds the freeze glock in EX.
Once thawed, the freeze_func acquires the freeze glock in SH and everybody
goes back to thawed.

Fixes: 541656d3a51 ("gfs2: freeze should work on read-only mounts")
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
---
 fs/gfs2/glops.c | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/fs/gfs2/glops.c b/fs/gfs2/glops.c
index 6c1432d78dce..67f2921ae8d4 100644
--- a/fs/gfs2/glops.c
+++ b/fs/gfs2/glops.c
@@ -571,7 +571,18 @@ static int freeze_go_sync(struct gfs2_glock *gl)
 	int error = 0;
 	struct gfs2_sbd *sdp = gl->gl_name.ln_sbd;
 
-	if (gl->gl_req == LM_ST_EXCLUSIVE && !gfs2_withdrawn(sdp)) {
+	/*
+	 * We need to check gl_state == LM_ST_SHARED here and not gl_req ==
+	 * LM_ST_EXCLUSIVE. That's because when any node does a freeze,
+	 * all the nodes should have the freeze glock in SH mode and they all
+	 * call do_xmote: One for EX and the others for UN. They ALL must
+	 * freeze locally, and they ALL must queue freeze work. The freeze_work
+	 * calls freeze_func, which tries to reacquire the freeze glock in SH,
+	 * effectively waiting for the thaw on the node who holds it in EX.
+	 * Once thawed, the work func acquires the freeze glock in
+	 * SH and everybody goes back to thawed.
+	 */
+	if (gl->gl_state == LM_ST_SHARED && !gfs2_withdrawn(sdp)) {
 		atomic_set(&sdp->sd_freeze_state, SFS_STARTING_FREEZE);
 		error = freeze_super(sdp->sd_vfs);
 		if (error) {



^ permalink raw reply related	[flat|nested] only message in thread

only message in thread, other threads:[~2020-11-17 19:40 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <796995883.26198021.1605642034293.JavaMail.zimbra@redhat.com>
2020-11-17 19:40 ` [Cluster-devel] [GFS2 PATCH] gfs2: Fix regression in freeze_go_sync Bob Peterson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).