From: syzbot <syzbot+9375e47164f8e9588f17@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: slab-out-of-bounds Read in poly1305_update_arch
Date: Tue, 01 Jul 2025 10:08:03 -0700 [thread overview]
Message-ID: <686415f3.a70a0220.3b7e22.1ec0.GAE@google.com> (raw)
In-Reply-To: <000000000000d62d530617ca4c33@google.com>
syzbot suspects this issue was fixed by commit:
commit d89a34b14df5c205de698c23c3950b2b947cdb97
Author: Alan Huang <mmpgouride@gmail.com>
Date: Sat Jun 14 09:18:07 2025 +0000
bcachefs: Move bset size check before csum check
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1460388c580000
start commit: 7367539ad4b0 Merge tag 'cxl-fixes-6.9-rc7' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=3714fc09f933e505
dashboard link: https://syzkaller.appspot.com/bug?extid=9375e47164f8e9588f17
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1196bc97180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11bc9a4c980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bcachefs: Move bset size check before csum check
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-07-01 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 14:58 [syzbot] [crypto?] KASAN: slab-out-of-bounds Read in poly1305_update_arch syzbot
2025-07-01 17:08 ` syzbot [this message]
2025-07-19 21:57 ` [syzbot] [bcachefs] " 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=686415f3.a70a0220.3b7e22.1ec0.GAE@google.com \
--to=syzbot+9375e47164f8e9588f17@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 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.