From: Bart Van Assche <bvanassche@acm.org>
To: Laibin Qiu <qiulaibin@huawei.com>,
jejb@linux.ibm.com, martin.petersen@oracle.com, hare@suse.de
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] [SCSI] Fix NULL pointer dereference in handling for passthrough commands
Date: Sat, 4 Sep 2021 21:49:36 -0700 [thread overview]
Message-ID: <388781f8-b9ce-abc2-148a-0498d32b6cb4@acm.org> (raw)
In-Reply-To: <20210904064534.1919476-1-qiulaibin@huawei.com>
On 9/3/21 23:45, Laibin Qiu wrote:
> In passthrough path. If the command size for ioctl request from userspace
> is 0. The original process will get cmd_len from cmd->cmnd, but It has
> not been assigned at this time. So it will trigger a NULL pointer BUG.
A Friday night in the middle of the merge window is not the best time to
post a kernel patch. Anyway:
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
prev parent reply other threads:[~2021-09-05 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 6:45 Laibin Qiu
2021-09-05 4:49 ` Bart Van Assche [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=388781f8-b9ce-abc2-148a-0498d32b6cb4@acm.org \
--to=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=qiulaibin@huawei.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
all inboxes | Powered by JetHome®