From: syzbot <syzbot+bfaeaa8e26281970158d@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, davem@davemloft.net,
herbert@gondor.apana.org.au, hpa@zytor.com,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, mmpgouride@gmail.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: [syzbot] [bcachefs?] KASAN: use-after-free Read in poly1305_update
Date: Sun, 15 Jun 2025 02:56:04 -0700 [thread overview]
Message-ID: <684e98b4.a00a0220.279073.002b.GAE@google.com> (raw)
In-Reply-To: <684c5575.a00a0220.279073.0012.GAE@google.com>
syzbot has bisected this issue to:
commit d97de0d017cde0d442c3d144b4f969f43064cc0f
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Tue Aug 13 01:31:25 2024 +0000
bcachefs: Make bkey_fsck_err() a wrapper around fsck_err()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1683290c580000
start commit: 02adc1490e6d Merge tag 'spi-fix-v6.16-rc1' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1583290c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1183290c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=162faeb2d1eaefb4
dashboard link: https://syzkaller.appspot.com/bug?extid=bfaeaa8e26281970158d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1555310c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12810e82580000
Reported-by: syzbot+bfaeaa8e26281970158d@syzkaller.appspotmail.com
Fixes: d97de0d017cd ("bcachefs: Make bkey_fsck_err() a wrapper around fsck_err()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-15 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 16:44 [syzbot] [bcachefs?] KASAN: use-after-free Read in poly1305_update syzbot
2025-06-15 9:56 ` syzbot [this message]
2025-07-19 21:56 ` 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=684e98b4.a00a0220.279073.002b.GAE@google.com \
--to=syzbot+bfaeaa8e26281970158d@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmpgouride@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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