From: syzbot <syzbot+99938118dfd9e1b0741a@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, axboe@kernel.dk,
bpf@vger.kernel.org, daniel@iogearbox.net, hch@lst.de,
john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
ming.lei@redhat.com, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
yhs@fb.com
Subject: Re: [syzbot] KASAN: use-after-free Read in bio_poll
Date: Mon, 09 May 2022 14:50:10 -0700 [thread overview]
Message-ID: <00000000000032d06e05de9b3136@google.com> (raw)
In-Reply-To: <00000000000029572505de968021@google.com>
syzbot has bisected this issue to:
commit 0f38d76646157357fcfa02f50575ea044830c494
Author: Christoph Hellwig <hch@lst.de>
Date: Tue Oct 12 10:40:45 2021 +0000
blk-mq: cleanup blk_mq_submit_bio
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12506f7ef00000
start commit: c5eb0a61238d Linux 5.18-rc6
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11506f7ef00000
console output: https://syzkaller.appspot.com/x/log.txt?x=16506f7ef00000
kernel config: https://syzkaller.appspot.com/x/.config?x=78013caa620443d6
dashboard link: https://syzkaller.appspot.com/bug?extid=99938118dfd9e1b0741a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1484cbc1f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10c7026cf00000
Reported-by: syzbot+99938118dfd9e1b0741a@syzkaller.appspotmail.com
Fixes: 0f38d7664615 ("blk-mq: cleanup blk_mq_submit_bio")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-05-09 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 16:14 [syzbot] KASAN: use-after-free Read in bio_poll syzbot
2022-05-09 17:02 ` Jens Axboe
2022-05-10 0:13 ` Ming Lei
2022-05-10 5:50 ` Christoph Hellwig
2022-05-10 12:45 ` Jens Axboe
2022-05-19 11:01 ` Dmitry Vyukov
2022-05-09 21:50 ` syzbot [this message]
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=00000000000032d06e05de9b3136@google.com \
--to=syzbot+99938118dfd9e1b0741a@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hch@lst.de \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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.