From: syzbot <syzbot+b23c4c9d3d228ba328d7@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, dvyukov@google.com,
jack@suse.cz, lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
luto@kernel.org, peterz@infradead.org, rafael@kernel.org,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, yukuai1@huaweicloud.com, yukuai3@huawei.com
Subject: Re: [syzbot] [reiserfs?] general protection fault in rcu_core (2)
Date: Mon, 04 Mar 2024 04:37:01 -0800 [thread overview]
Message-ID: <0000000000007cb7130612d4fb95@google.com> (raw)
In-Reply-To: <0000000000009dc57505fd85ceb9@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=14e58b32180000
start commit: e8f75c0270d9 Merge tag 'x86_sgx_for_v6.5' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a98ec7f738e43bd4
dashboard link: https://syzkaller.appspot.com/bug?extid=b23c4c9d3d228ba328d7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12d6dfc0a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=161de580a80000
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-03-04 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 8:20 [syzbot] [reiserfs?] general protection fault in rcu_core (2) syzbot
2023-06-14 22:20 ` syzbot
2023-06-15 2:15 ` Yu Kuai
2023-06-15 7:33 ` Dmitry Vyukov
2024-03-04 12:37 ` 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=0000000000007cb7130612d4fb95@google.com \
--to=syzbot+b23c4c9d3d228ba328d7@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dvyukov@google.com \
--cc=jack@suse.cz \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@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 read-only IMAP folder(s) and NNTP newsgroup(s).