From: syzbot <syzbot+2b3f18414c37b42dcc94@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, kch@nvidia.com,
kpsingh@kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
yhs@fb.com
Subject: Re: [syzbot] general protection fault in submit_bio_checks
Date: Thu, 03 Feb 2022 13:06:09 -0800 [thread overview]
Message-ID: <000000000000dade8505d72380c9@google.com> (raw)
In-Reply-To: <0000000000008c32e305d6d8e802@google.com>
syzbot has bisected this issue to:
commit a7c50c940477bae89fb2b4f51bd969a2d95d7512
Author: Christoph Hellwig <hch@lst.de>
Date: Mon Jan 24 09:11:07 2022 +0000
block: pass a block_device and opf to bio_reset
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12b4f1cc700000
start commit: 2d3d8c7643a5 Add linux-next specific files for 20220203
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=11b4f1cc700000
console output: https://syzkaller.appspot.com/x/log.txt?x=16b4f1cc700000
kernel config: https://syzkaller.appspot.com/x/.config?x=27a9abf2c11167c7
dashboard link: https://syzkaller.appspot.com/bug?extid=2b3f18414c37b42dcc94
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14635480700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10eb2d14700000
Reported-by: syzbot+2b3f18414c37b42dcc94@syzkaller.appspotmail.com
Fixes: a7c50c940477 ("block: pass a block_device and opf to bio_reset")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-02-03 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 4:06 [syzbot] general protection fault in submit_bio_checks syzbot
2022-02-03 18:21 ` syzbot
2022-02-03 21:06 ` syzbot [this message]
2022-02-03 21:20 ` Jens Axboe
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=000000000000dade8505d72380c9@google.com \
--to=syzbot+2b3f18414c37b42dcc94@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=kch@nvidia.com \
--cc=kpsingh@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.