[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251116201224.2151726-1-agruenba@redhat.com>
Date: Sun, 16 Nov 2025 20:12:23 +0000
From: Andreas Gruenbacher <agruenba@...hat.com>
To: Nirbhay Sharma <nirbhay.lkd@...il.com>
Cc: Andreas Gruenbacher <agruenba@...hat.com>,
gfs2@...ts.linux.dev,
linux-kernel@...r.kernel.org,
syzbot+19e0be39cc25dfcb0858@...kaller.appspotmail.com,
skhan@...uxfoundation.org,
david.hunter.linux@...il.com,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: Re: [PATCH] gfs2: flush withdraw work before freeing gfs2_sbd
Hi Nirbhay,
On Thu, Nov 13, 2025 at 9:24 PM Nirbhay Sharma <nirbhay.lkd@...il.com> wrote:
> Hi Andreas,
>
> I hope this email finds you well.
>
> I'm writing to follow up on the GFS2 patch I submitted regarding the ODEBUG warning in free_sbd(). The patch addressed the syzbot report where sd_withdraw_work was being freed while still active.
>
> I wanted to check if you've had a chance to review the patch, or if there's any feedback or additional information I can provide to help with the review process.
>
> I understand maintainers are busy, and I'm happy to make any necessary revisions or provide further clarification on the testing that was performed.
thanks for looking into this issue, but this is already fixed in the
updated version of patch "gfs2: Asynchronous withdraw" which has been on
gfs2 for-next since at least October 23. Below is my isolated fix.
Thanks,
Andreas
diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
index 2d177aa21ffd..c42982bdd4b2 100644
--- a/fs/gfs2/ops_fstype.c
+++ b/fs/gfs2/ops_fstype.c
@@ -1294,7 +1294,6 @@ static int gfs2_fill_super(struct super_block *sb, struct fs_context *fc)
fail_per_node:
init_per_node(sdp, UNDO);
fail_inodes:
- flush_work(&sdp->sd_withdraw_work);
init_inodes(sdp, UNDO);
fail_sb:
if (sdp->sd_root_dir)
diff --git a/fs/gfs2/util.c b/fs/gfs2/util.c
index fff0b0e2e27c..c454bea101de 100644
--- a/fs/gfs2/util.c
+++ b/fs/gfs2/util.c
@@ -345,6 +345,12 @@ void gfs2_withdraw(struct gfs2_sbd *sdp)
} while (unlikely(!try_cmpxchg(&sdp->sd_flags, &old, new)));
dump_stack();
+ /*
+ * There is no need to withdraw when the superblock hasn't been
+ * fully initialized, yet.
+ */
+ if (!(sdp->sd_vfs->s_flags & SB_BORN))
+ return;
fs_err(sdp, "about to withdraw this file system\n");
schedule_work(&sdp->sd_withdraw_work);
}
Powered by blists - more mailing lists