From: Douglas Gilbert <dgilbert@interlog.com>
To: Wu Bo <wubo40@huawei.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
liuzhiqiang26@huawei.com, linfeilong@huawei.com
Subject: Re: [PATCH] scsi:sg: add sg_remove_request in sg_write
Date: Tue, 14 Apr 2020 14:44:51 -0400 [thread overview]
Message-ID: <4ece8e46-f9e4-e582-157a-7ab0268c04aa@interlog.com> (raw)
In-Reply-To: <610618d9-e983-fd56-ed0f-639428343af7@huawei.com>
On 2020-04-13 10:13 p.m., Wu Bo wrote:
> From: Wu Bo <wubo40@huawei.com>
>
> If the __copy_from_user function return failed,
> it should call sg_remove_request in sg_write.
This is a fix.
Acked-by: Douglas Gilbert <dgilbert@interlog.com>
> Signed-off-by: Wu Bo <wubo40@huawei.com>
> ---
> drivers/scsi/sg.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/sg.c b/drivers/scsi/sg.c
> index 4e6af59..ff3f532 100644
> --- a/drivers/scsi/sg.c
> +++ b/drivers/scsi/sg.c
> @@ -685,8 +685,10 @@ static int get_sg_io_pack_id(int *pack_id, void __user
> *buf, size_t count)
> hp->flags = input_size; /* structure abuse ... */
> hp->pack_id = old_hdr.pack_id;
> hp->usr_ptr = NULL;
> - if (copy_from_user(cmnd, buf, cmd_size))
> + if (copy_from_user(cmnd, buf, cmd_size)) {
> + sg_remove_request(sfp, srp);
> return -EFAULT;
> + }
> /*
> * SG_DXFER_TO_FROM_DEV is functionally equivalent to SG_DXFER_FROM_DEV,
> * but is is possible that the app intended SG_DXFER_TO_DEV, because there
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2020-04-14 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 2:13 Wu Bo
2020-04-14 18:44 ` Douglas Gilbert [this message]
2020-04-15 1:18 ` Martin K. Petersen
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=4ece8e46-f9e4-e582-157a-7ab0268c04aa@interlog.com \
--to=dgilbert@interlog.com \
--cc=jejb@linux.ibm.com \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=wubo40@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®