cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/3] gfs2: Prevent double iput for journal on error
Date: Wed, 27 Jul 2022 11:02:20 -0500	[thread overview]
Message-ID: <20220727160222.227803-2-rpeterso@redhat.com> (raw)
In-Reply-To: <20220727160222.227803-1-rpeterso@redhat.com>

When a gfs2 file system is withdrawn, it requests recovery from another
cluster node. To do that, it evicts its journal from memory, but it
keeps the journal entry queued to the journals queue, jindex_list. After
recovery it tries to grab a new inode for its (recovered) journal. If it
cannot, it skips further recovery but its evicted journal is still on
the jindex list, which means unmount will try to iput it a second time
after it's been evicted. This second iput causes vfs to complain and BUG
out:

kernel BUG at fs/inode.c:1680!

To prevent this, this patch takes steps to dequeue the journal
descriptor from the list when it cannot get a replacement inode. So
unmount won't find it on the list and try to iput it again.

Signed-off-by: Bob Peterson <rpeterso@redhat.com>
---
 fs/gfs2/util.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/fs/gfs2/util.c b/fs/gfs2/util.c
index 8241029a2a5d..78cb12d0fba1 100644
--- a/fs/gfs2/util.c
+++ b/fs/gfs2/util.c
@@ -275,6 +275,17 @@ static void signal_our_withdraw(struct gfs2_sbd *sdp)
 	if (IS_ERR(inode)) {
 		fs_warn(sdp, "Reprocessing of jid %d failed with %ld.\n",
 			sdp->sd_lockstruct.ls_jid, PTR_ERR(inode));
+		/*
+		 * We couldn't get a replacement inode for our journal but we
+		 * evicted the old one. So dequeue it from the journals queue,
+		 * jindex_list, so that unmount doesn't do iput on it twice.
+		 */
+		spin_lock(&sdp->sd_jindex_spin);
+		list_del(&sdp->sd_jdesc->jd_list);
+		sdp->sd_journals--;
+		spin_unlock(&sdp->sd_jindex_spin);
+		kfree(sdp->sd_jdesc);
+		sdp->sd_jdesc = NULL;
 		goto skip_recovery;
 	}
 	sdp->sd_jdesc->jd_inode = inode;
-- 
2.36.1


  reply	other threads:[~2022-07-27 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 16:02 [Cluster-devel] [PATCH 0/3] Misc withdraw patches Bob Peterson
2022-07-27 16:02 ` Bob Peterson [this message]
2022-08-02 14:37   ` [Cluster-devel] [PATCH 1/3] gfs2: Prevent double iput for journal on error Andreas Gruenbacher
2022-07-27 16:02 ` [Cluster-devel] [PATCH 2/3] gfs2: Dequeue waiters when withdrawn Bob Peterson
2022-08-02 14:47   ` Andreas Gruenbacher
2022-07-27 16:02 ` [Cluster-devel] [PATCH 3/3] gfs2: Clear GLF_LOCK when withdraw prevents xmote Bob Peterson
  -- strict thread matches above, loose matches on Subject: below --
2022-08-02 17:58 [Cluster-devel] [PATCH v2 0/3] gfs2: Misc withdraw patches Bob Peterson
2022-08-02 17:58 ` [Cluster-devel] [PATCH 1/3] gfs2: Prevent double iput for journal on error Bob Peterson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220727160222.227803-2-rpeterso@redhat.com \
    --to=rpeterso@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).