From: syzbot <syzbot+ae4dc916da3ce51f284f@syzkaller.appspotmail.com>
To: bfoster@redhat.com, kent.overstreet@linux.dev,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in __bch2_bkey_invalid
Date: Mon, 06 May 2024 02:36:04 -0700 [thread overview]
Message-ID: <0000000000005a730f0617c5cc76@google.com> (raw)
In-Reply-To: <0000000000005c46090617b917e7@google.com>
syzbot has bisected this issue to:
commit d789e9a7d5e2799f4d5425b0b620210d2fcad529
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sun Apr 14 03:59:28 2024 +0000
bcachefs: Interior known are required to have known key types
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1070e9df180000
start commit: b9158815de52 Merge tag 'char-misc-6.9-rc7' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1270e9df180000
console output: https://syzkaller.appspot.com/x/log.txt?x=1470e9df180000
kernel config: https://syzkaller.appspot.com/x/.config?x=d2f00edef461175
dashboard link: https://syzkaller.appspot.com/bug?extid=ae4dc916da3ce51f284f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11a910c4980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15490b54980000
Reported-by: syzbot+ae4dc916da3ce51f284f@syzkaller.appspotmail.com
Fixes: d789e9a7d5e2 ("bcachefs: Interior known are required to have known key types")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-05-06 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 18:26 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in __bch2_bkey_invalid syzbot
2024-05-06 9:36 ` 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=0000000000005a730f0617c5cc76@google.com \
--to=syzbot+ae4dc916da3ce51f284f@syzkaller.appspotmail.com \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).