From: syzbot <syzbot+8c4acf719c3fc41e8439@syzkaller.appspotmail.com>
To: bfoster@redhat.com, davem@davemloft.net,
herbert@gondor.apana.org.au, kent.overstreet@linux.dev,
linux-bcachefs@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs] KASAN: use-after-free Read in scatterwalk_copychunks
Date: Sat, 04 May 2024 17:35:04 -0700 [thread overview]
Message-ID: <000000000000bdedb60617aa1f12@google.com> (raw)
In-Reply-To: <0000000000003392c606179ddd1a@google.com>
syzbot has bisected this issue to:
commit dc6f2eb000d76ac8f93f4d59a8012ddfccca927a
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Wed Apr 17 05:26:02 2024 +0000
bcachefs: make btree read errors silent during scan
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16629450980000
start commit: 9221b2819b8a Add linux-next specific files for 20240503
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=15629450980000
console output: https://syzkaller.appspot.com/x/log.txt?x=11629450980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8ab537f51a6a0d98
dashboard link: https://syzkaller.appspot.com/bug?extid=8c4acf719c3fc41e8439
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=111abc97180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10059004980000
Reported-by: syzbot+8c4acf719c3fc41e8439@syzkaller.appspotmail.com
Fixes: dc6f2eb000d7 ("bcachefs: make btree read errors silent during scan")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-05-05 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 9:57 [syzbot] [crypto?] KASAN: use-after-free Read in scatterwalk_copychunks syzbot
2024-05-04 9:58 ` Aleksandr Nogikh
2024-05-05 0:35 ` syzbot [this message]
2025-04-30 20:35 ` [syzbot] [bcachefs] " 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=000000000000bdedb60617aa1f12@google.com \
--to=syzbot+8c4acf719c3fc41e8439@syzkaller.appspotmail.com \
--cc=bfoster@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-crypto@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 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.