From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+d34c2a269ed512c531b0@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] BUG: corrupted list in gfs2_fill_super
Date: Sun, 2 Jun 2024 17:50:24 +0800 [thread overview]
Message-ID: <20240602095024.3791-1-hdanton@sina.com> (raw)
In-Reply-To: <0000000000002501960619e2366b@google.com>
On Sat, 01 Jun 2024 23:20:21 -0700
> syzbot found the following issue on:
>
> HEAD commit: 9d99040b1bc8 Add linux-next specific files for 20240529
> git tree: linux-next
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=100817e6980000
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
--- x/fs/gfs2/ops_fstype.c
+++ y/fs/gfs2/ops_fstype.c
@@ -1137,6 +1137,7 @@ static int gfs2_fill_super(struct super_
struct gfs2_sbd *sdp;
struct gfs2_holder mount_gh;
int error;
+ int destroyed = 0;
sdp = init_sbd(sb);
if (!sdp) {
@@ -1301,6 +1302,7 @@ fail_locking:
fail_lm:
complete_all(&sdp->sd_journal_ready);
gfs2_gl_hash_clear(sdp);
+ destroyed = 1;
gfs2_lm_unmount(sdp);
fail_debug:
gfs2_delete_debugfs_file(sdp);
@@ -1308,7 +1310,8 @@ fail_debug:
fail_delete_wq:
destroy_workqueue(sdp->sd_delete_wq);
fail_glock_wq:
- destroy_workqueue(sdp->sd_glock_wq);
+ if (!destroyed)
+ destroy_workqueue(sdp->sd_glock_wq);
fail_free:
free_sbd(sdp);
sb->s_fs_info = NULL;
--
next prev parent reply other threads:[~2024-06-02 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 6:20 syzbot
2024-06-02 9:50 ` Hillf Danton [this message]
2024-06-02 10:23 ` syzbot
2024-07-11 11:00 ` syzbot
2024-07-21 22:11 ` syzbot
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=20240602095024.3791-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+d34c2a269ed512c531b0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®