From: syzbot <syzbot+427fed3295e9a7e887f2@syzkaller.appspotmail.com>
To: agruenba@redhat.com, axboe@kernel.dk, brauner@kernel.org,
cluster-devel@redhat.com, elver@google.com,
gfs2@lists.linux.dev, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
nogikh@google.com, peterz@infradead.org, rpeterso@redhat.com,
syzkaller-bugs@googlegroups.com, valentin.schneider@arm.com
Subject: Re: [syzbot] [gfs2?] general protection fault in gfs2_dump_glock (2)
Date: Mon, 19 Feb 2024 03:58:05 -0800 [thread overview]
Message-ID: <00000000000077ce280611bace5b@google.com> (raw)
In-Reply-To: <00000000000050a49105f63ed997@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=14238a3c180000
start commit: 58390c8ce1bd Merge tag 'iommu-updates-v6.4' of git://git.k..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=5eadbf0d3c2ece89
dashboard link: https://syzkaller.appspot.com/bug?extid=427fed3295e9a7e887f2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=172bead8280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d01d08280000
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 prev parent reply other threads:[~2024-02-19 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 17:44 [syzbot] [cluster?] general protection fault in gfs2_dump_glock (2) syzbot
2023-09-05 1:55 ` [syzbot] [gfs2?] " syzbot
2023-09-05 9:57 ` Aleksandr Nogikh
2024-02-19 11:58 ` syzbot [this message]
2024-02-19 12:56 ` 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=00000000000077ce280611bace5b@google.com \
--to=syzbot+427fed3295e9a7e887f2@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cluster-devel@redhat.com \
--cc=elver@google.com \
--cc=gfs2@lists.linux.dev \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=peterz@infradead.org \
--cc=rpeterso@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=valentin.schneider@arm.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).