From: syzbot <syzbot+e577022d4fba380653be@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v1_to_text
Date: Wed, 11 Jun 2025 11:25:02 -0700 [thread overview]
Message-ID: <6849c9fe.a00a0220.1eb5f5.00f4.GAE@google.com> (raw)
In-Reply-To: <68488453.a70a0220.27c366.0067.GAE@google.com>
syzbot has bisected this issue to:
commit c5ae261c8095a37174e17eb13c5485cbd1b3bb20
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sun Jun 8 15:31:23 2025 +0000
bcachefs: Don't trust sb->nr_devices in members_to_text()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15a6ad70580000
start commit: b27cc623e01b Add linux-next specific files for 20250610
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=17a6ad70580000
console output: https://syzkaller.appspot.com/x/log.txt?x=13a6ad70580000
kernel config: https://syzkaller.appspot.com/x/.config?x=846e731334efc0f8
dashboard link: https://syzkaller.appspot.com/bug?extid=e577022d4fba380653be
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a5e9d4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1766260c580000
Reported-by: syzbot+e577022d4fba380653be@syzkaller.appspotmail.com
Fixes: c5ae261c8095 ("bcachefs: Don't trust sb->nr_devices in members_to_text()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-11 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 19:15 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v1_to_text syzbot
2025-06-11 18:25 ` syzbot [this message]
2025-07-20 4:06 ` Forwarded: 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=6849c9fe.a00a0220.1eb5f5.00f4.GAE@google.com \
--to=syzbot+e577022d4fba380653be@syzkaller.appspotmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.