From: syzbot <syzbot+f57d864a5d6eff90da3b@syzkaller.appspotmail.com>
To: bfoster@redhat.com, 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_stripe_validate
Date: Sun, 27 Apr 2025 08:10:03 -0700 [thread overview]
Message-ID: <680e48cb.a70a0220.23e4d2.0024.GAE@google.com> (raw)
In-Reply-To: <6772228e.050a0220.2f3838.04b8.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 71f8e806a5e4edada72456ee3b2e2d7eab6fadee
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Fri Apr 18 16:49:00 2025 +0000
bcachefs: Stricter checks on "key allowed in this btree"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16b9e270580000
start commit: ccb98ccef0e5 Merge tag 'platform-drivers-x86-v6.13-4' of g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ba7cde9482d6bb6
dashboard link: https://syzkaller.appspot.com/bug?extid=f57d864a5d6eff90da3b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=131666df980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10556ac4580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bcachefs: Stricter checks on "key allowed in this btree"
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-04-27 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 4:33 [syzbot] [bcachefs?] kernel BUG in bch2_stripe_validate syzbot
2024-12-31 14:07 ` syzbot
2025-04-27 15:10 ` syzbot [this message]
2025-04-27 19:16 ` 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=680e48cb.a70a0220.23e4d2.0024.GAE@google.com \
--to=syzbot+f57d864a5d6eff90da3b@syzkaller.appspotmail.com \
--cc=bfoster@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox