From: syzbot <syzbot+ed7d0f71a89e28557a77@syzkaller.appspotmail.com>
To: agruenba@redhat.com, axboe@kernel.dk, bobo.shaobowang@huawei.com,
brauner@kernel.org, broonie@kernel.org, catalin.marinas@arm.com,
cluster-devel@redhat.com, dominic.coppola@gatoradeadvert.com,
dvyukov@google.com, gfs2@lists.linux.dev, jack@suse.cz,
liaoyu15@huawei.com, linux-arm-kernel@lists.infradead.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
liwei391@huawei.com, madvenka@linux.microsoft.com,
rpeterso@redhat.com, scott@os.amperecomputing.com,
syzkaller-bugs@googlegroups.com, will@kernel.org
Subject: Re: [syzbot] [gfs2?] INFO: task hung in gfs2_gl_hash_clear (3)
Date: Sun, 21 Jan 2024 20:21:05 -0800 [thread overview]
Message-ID: <00000000000081bcbd060f8128e2@google.com> (raw)
In-Reply-To: <000000000000d482ba05ee97d4e3@google.com>
syzbot suspects this issue was fixed by commit:
commit 6f861765464f43a71462d52026fbddfc858239a5
Author: Jan Kara <jack@suse.cz>
Date: Wed Nov 1 17:43:10 2023 +0000
fs: Block writes to mounted block devices
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=137b2d43e80000
start commit: 3f01e9fed845 Merge tag 'linux-watchdog-6.5-rc2' of git://w..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=29fd3392a08741ef
dashboard link: https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17b6f3f8a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1688b6d4a80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs: Block writes to mounted block devices
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2024-01-22 4:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000d482ba05ee97d4e3@google.com>
2024-01-22 4:21 ` syzbot [this message]
2024-01-23 9:05 ` [syzbot] [gfs2?] INFO: task hung in gfs2_gl_hash_clear (3) Jan Kara
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=00000000000081bcbd060f8128e2@google.com \
--to=syzbot+ed7d0f71a89e28557a77@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=axboe@kernel.dk \
--cc=bobo.shaobowang@huawei.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cluster-devel@redhat.com \
--cc=dominic.coppola@gatoradeadvert.com \
--cc=dvyukov@google.com \
--cc=gfs2@lists.linux.dev \
--cc=jack@suse.cz \
--cc=liaoyu15@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=madvenka@linux.microsoft.com \
--cc=rpeterso@redhat.com \
--cc=scott@os.amperecomputing.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).