From: syzbot <syzbot+cd063f869beedf5b9cd7@syzkaller.appspotmail.com>
To: bfoster@redhat.com, elver@google.com, justinstitt@google.com,
keescook@chromium.org, kent.overstreet@linux.dev,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
mmpgouride@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] UBSAN: array-index-out-of-bounds in bch2_accounting_validate
Date: Mon, 04 Aug 2025 10:26:04 -0700 [thread overview]
Message-ID: <6890ed2c.050a0220.1fc43d.0010.GAE@google.com> (raw)
In-Reply-To: <68905ecc.050a0220.7f033.0004.GAE@google.com>
syzbot has bisected this issue to:
commit 557f8c582a9ba8abe6aa0fd734b6f342af106b26
Author: Kees Cook <keescook@chromium.org>
Date: Thu Jan 18 23:06:05 2024 +0000
ubsan: Reintroduce signed overflow sanitizer
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=161982f0580000
start commit: 352af6a011d5 Merge tag 'rust-6.17' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=151982f0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=111982f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cae1291240e8962a
dashboard link: https://syzkaller.appspot.com/bug?extid=cd063f869beedf5b9cd7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14dcc6a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=133e02f0580000
Reported-by: syzbot+cd063f869beedf5b9cd7@syzkaller.appspotmail.com
Fixes: 557f8c582a9b ("ubsan: Reintroduce signed overflow sanitizer")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-08-04 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 7:18 [syzbot] [bcachefs?] UBSAN: array-index-out-of-bounds in bch2_accounting_validate syzbot
2025-08-04 12:18 ` Alan Huang
2025-08-04 12:19 ` syzbot
2025-08-04 12:21 ` Alan Huang
2025-08-04 19:30 ` syzbot
2025-08-04 17:26 ` syzbot [this message]
2025-08-04 22:56 ` 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=6890ed2c.050a0220.1fc43d.0010.GAE@google.com \
--to=syzbot+cd063f869beedf5b9cd7@syzkaller.appspotmail.com \
--cc=bfoster@redhat.com \
--cc=elver@google.com \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmpgouride@gmail.com \
--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.