From: James Bottomley <jejb@linux.ibm.com>
To: syzbot <syzbot+0796b72dc61f223d8cc5@syzkaller.appspotmail.com>,
hare@suse.de, hch@lst.de, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in scsi_queue_rq
Date: Tue, 13 Oct 2020 16:08:09 -0700 [thread overview]
Message-ID: <95f493a39c2a6cc2f45da2f7fe73d7febee927df.camel@linux.ibm.com> (raw)
In-Reply-To: <00000000000047627e05b17a6ec9@google.com>
On Mon, 2020-10-12 at 07:51 -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: e4fb79c7 Add linux-next specific files for 20201008
> git tree: linux-next
> console output:
> https://syzkaller.appspot.com/x/log.txt?x=125c9a9f900000
> kernel config:
> https://syzkaller.appspot.com/x/.config?x=568d41fe4341ed0f
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=0796b72dc61f223d8cc5
> compiler: gcc (GCC) 10.1.0-syz 20200507
> syz repro:
> https://syzkaller.appspot.com/x/repro.syz?x=12582fe7900000
> C reproducer:
> https://syzkaller.appspot.com/x/repro.c?x=124ac7d0500000
>
> The issue was bisected to:
>
> commit 2ceda20f0a99a74a82b78870f3b3e5fa93087a7f
> Author: Christoph Hellwig <hch@lst.de>
> Date: Mon Oct 5 08:41:23 2020 +0000
>
> scsi: core: Move command size detection out of the fast path
#syz: test git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-misc
next prev parent reply other threads:[~2020-10-13 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 14:51 general protection fault in scsi_queue_rq syzbot
2020-10-13 23:08 ` James Bottomley [this message]
2020-10-14 0:45 ` syzbot
2021-12-12 0:29 ` [syzbot] " syzbot
2021-12-13 7:13 ` Dmitry Vyukov
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=95f493a39c2a6cc2f45da2f7fe73d7febee927df.camel@linux.ibm.com \
--to=jejb@linux.ibm.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=syzbot+0796b72dc61f223d8cc5@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox