From: syzbot <syzbot+4908f37148402680dfec@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?] kernel BUG in __bch2_bkey_compat
Date: Sun, 15 Jun 2025 08:38:01 -0700 [thread overview]
Message-ID: <684ee8d9.050a0220.be214.02c0.GAE@google.com> (raw)
In-Reply-To: <684c57c4.a00a0220.279073.0015.GAE@google.com>
syzbot has bisected this issue to:
commit cd3cdb1ef706a1ac725194d81858d58375739b25
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Tue Apr 22 13:14:19 2025 +0000
bcachefs: Single err message for btree node reads
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11b67d70580000
start commit: 27605c8c0f69 Merge tag 'net-6.16-rc2' of git://git.kernel...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=13b67d70580000
console output: https://syzkaller.appspot.com/x/log.txt?x=15b67d70580000
kernel config: https://syzkaller.appspot.com/x/.config?x=162faeb2d1eaefb4
dashboard link: https://syzkaller.appspot.com/bug?extid=4908f37148402680dfec
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10f9f682580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ecb9d4580000
Reported-by: syzbot+4908f37148402680dfec@syzkaller.appspotmail.com
Fixes: cd3cdb1ef706 ("bcachefs: Single err message for btree node reads")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-15 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 16:54 [syzbot] [bcachefs?] kernel BUG in __bch2_bkey_compat syzbot
2025-06-15 15:38 ` syzbot [this message]
2025-07-14 6:32 ` syzbot
2025-07-19 18:36 ` Kent Overstreet
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=684ee8d9.050a0220.be214.02c0.GAE@google.com \
--to=syzbot+4908f37148402680dfec@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.