From: syzbot <syzbot+d587b24799bd8c2d32f4@syzkaller.appspotmail.com>
To: bfoster@redhat.com, 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, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: [syzbot] [bcachefs] KASAN: use-after-free Read in crypto_poly1305_update
Date: Tue, 18 Feb 2025 14:05:02 -0800 [thread overview]
Message-ID: <67b5040e.050a0220.14d86d.0013.GAE@google.com> (raw)
In-Reply-To: <67b2eaf8.050a0220.173698.0020.GAE@google.com>
syzbot has bisected this issue to:
commit 03ef80b469d5d83530ce1ce15be78a40e5300f9b
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sat Sep 23 22:41:51 2023 +0000
bcachefs: Ignore unknown mount options
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15a303a4580000
start commit: 2408a807bfc3 Merge tag 'vfs-6.14-rc4.fixes' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17a303a4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=13a303a4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6cc40dfe827ffb85
dashboard link: https://syzkaller.appspot.com/bug?extid=d587b24799bd8c2d32f4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c4f2e4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e4c498580000
Reported-by: syzbot+d587b24799bd8c2d32f4@syzkaller.appspotmail.com
Fixes: 03ef80b469d5 ("bcachefs: Ignore unknown mount options")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-02-18 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 7:53 [syzbot] [crypto?] " syzbot
2025-02-17 10:24 ` Ard Biesheuvel
2025-02-18 22:05 ` syzbot [this message]
2025-07-17 20:49 ` [syzbot] [bcachefs] " syzbot
2025-07-17 21:45 ` 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=67b5040e.050a0220.14d86d.0013.GAE@google.com \
--to=syzbot+d587b24799bd8c2d32f4@syzkaller.appspotmail.com \
--cc=bfoster@redhat.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=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
all inboxes | Powered by JetHome®