From: syzbot <syzbot+b23c4c9d3d228ba328d7@syzkaller.appspotmail.com>
To: jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, luto@kernel.org,
peterz@infradead.org, reiserfs-devel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
yukuai3@huawei.com
Subject: Re: [syzbot] [reiserfs?] general protection fault in rcu_core (2)
Date: Wed, 14 Jun 2023 15:20:35 -0700 [thread overview]
Message-ID: <000000000000556d9605fe1e5c40@google.com> (raw)
In-Reply-To: <0000000000009dc57505fd85ceb9@google.com>
syzbot has bisected this issue to:
commit 2acf15b94d5b8ea8392c4b6753a6ffac3135cd78
Author: Yu Kuai <yukuai3@huawei.com>
Date: Fri Jul 2 04:07:43 2021 +0000
reiserfs: add check for root_inode in reiserfs_fill_super
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1715ffdd280000
start commit: f8dba31b0a82 Merge tag 'asym-keys-fix-for-linus-v6.4-rc5' ..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1495ffdd280000
console output: https://syzkaller.appspot.com/x/log.txt?x=1095ffdd280000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c980bfe8b399968
dashboard link: https://syzkaller.appspot.com/bug?extid=b23c4c9d3d228ba328d7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1680f7d1280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12fad50d280000
Reported-by: syzbot+b23c4c9d3d228ba328d7@syzkaller.appspotmail.com
Fixes: 2acf15b94d5b ("reiserfs: add check for root_inode in reiserfs_fill_super")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-06-14 22:20 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 [this message]
2023-06-15 2:15 ` Yu Kuai
2023-06-15 7:33 ` Dmitry Vyukov
2024-03-04 12:37 ` 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=000000000000556d9605fe1e5c40@google.com \
--to=syzbot+b23c4c9d3d228ba328d7@syzkaller.appspotmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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 NNTP newsgroup(s).