From: syzbot <syzbot+0796b72dc61f223d8cc5@syzkaller.appspotmail.com>
To: anmol.karan123@gmail.com, capitolscan@capitolsecuritypr.com,
hare@suse.de, hch@lst.de, jejb@linux.ibm.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com, syzkaller-bugs@googlegroups.com,
tadeusz.struk@linaro.org
Subject: Re: [syzbot] general protection fault in scsi_queue_rq
Date: Sat, 11 Dec 2021 16:29:13 -0800 [thread overview]
Message-ID: <000000000000b17d0105d2e80b47@google.com> (raw)
In-Reply-To: <00000000000047627e05b17a6ec9@google.com>
syzbot suspects this issue was fixed by commit:
commit 20aaef52eb08f1d987d46ad26edb8f142f74d83a
Author: Tadeusz Struk <tadeusz.struk@linaro.org>
Date: Wed Nov 3 17:06:58 2021 +0000
scsi: scsi_ioctl: Validate command size
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11db6f3ab00000
start commit: ec681c53f8d2 Merge tag 'net-5.15-rc6' of git://git.kernel...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=bab9d35f204746a7
dashboard link: https://syzkaller.appspot.com/bug?extid=0796b72dc61f223d8cc5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1279df24b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15a855f4b00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: scsi: scsi_ioctl: Validate command size
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-12-12 0:29 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
2020-10-14 0:45 ` syzbot
2021-12-12 0:29 ` syzbot [this message]
2021-12-13 7:13 ` [syzbot] " 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=000000000000b17d0105d2e80b47@google.com \
--to=syzbot+0796b72dc61f223d8cc5@syzkaller.appspotmail.com \
--cc=anmol.karan123@gmail.com \
--cc=capitolscan@capitolsecuritypr.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tadeusz.struk@linaro.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