From: syzbot <syzbot+6820505ae5978f4f8f2f@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, alaaemadhossney.ae@gmail.com,
alex.shi@linux.alibaba.com, axboe@kernel.dk,
baijiaju1990@gmail.com, brauner@kernel.org,
colin.king@canonical.com, dhowells@redhat.com,
gregkh@linuxfoundation.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@kernel.org, rdunlap@infradead.org,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
yanaijie@huawei.com, zhengbin13@huawei.com
Subject: Re: [syzbot] [reiserfs?] kernel BUG at fs/reiserfs/journal.c:LINE!
Date: Sun, 25 Feb 2024 20:09:03 -0800 [thread overview]
Message-ID: <000000000000ec5a2f0612411136@google.com> (raw)
In-Reply-To: <001a113eba282f2ffc0568b76123@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=16fcca02180000
start commit: b85ea95d0864 Linux 6.7-rc1
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=b5bf1661f609e7f0
dashboard link: https://syzkaller.appspot.com/bug?extid=6820505ae5978f4f8f2f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1728c947680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1079c598e80000
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
prev parent reply other threads:[~2024-02-26 4:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 15:55 kernel BUG at fs/reiserfs/journal.c:LINE! syzbot
2020-09-19 15:30 ` syzbot
2024-02-26 4:09 ` syzbot [this message]
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=000000000000ec5a2f0612411136@google.com \
--to=syzbot+6820505ae5978f4f8f2f@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=alaaemadhossney.ae@gmail.com \
--cc=alex.shi@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=baijiaju1990@gmail.com \
--cc=brauner@kernel.org \
--cc=colin.king@canonical.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rdunlap@infradead.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yanaijie@huawei.com \
--cc=zhengbin13@huawei.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).