From: Jason Yan <yanaijie@huawei.com>
To: Hannes Reinecke <hare@suse.de>, <axboe@kernel.dk>,
<ming.lei@redhat.com>, <hch@lst.de>, <keescook@chromium.org>,
<kbusch@kernel.org>, <linux-block@vger.kernel.org>,
<martin.petersen@oracle.com>, <jejb@linux.vnet.ibm.com>
Cc: <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2/3] scsi: only copy data to user when the whole result is good
Date: Fri, 19 Mar 2021 16:22:15 +0800 [thread overview]
Message-ID: <ce784b08-b020-f67e-d902-a15affbdb1ca@huawei.com> (raw)
In-Reply-To: <7279b268-0b57-c78a-b189-75e1515c7166@suse.de>
Hi Hannes,
在 2021/3/19 15:56, Hannes Reinecke 写道:
> On 3/19/21 4:01 AM, Jason Yan wrote:
>> When the scsi device status is offline, mode sense command will return a
>> result with only DID_NO_CONNECT set. Then in sg_scsi_ioctl(),
>> only status byte of the result is checked, and because of
>> bug [1], garbage data is copied to the userspace.
>>
>> Only copy the buffer to userspace when the whole result is good.
>>
>> [1]
>> https://patchwork.kernel.org/project/linux-block/patch/20210318122621.330010-1-yanaijie@huawei.com/
>>
>>
>> Signed-off-by: Jason Yan <yanaijie@huawei.com>
>> ---
>> block/scsi_ioctl.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/block/scsi_ioctl.c b/block/scsi_ioctl.c
>> index 6599bac0a78c..359bf0003af4 100644
>> --- a/block/scsi_ioctl.c
>> +++ b/block/scsi_ioctl.c
>> @@ -503,7 +503,7 @@ int sg_scsi_ioctl(struct request_queue *q, struct
>> gendisk *disk, fmode_t mode,
>> if (copy_to_user(sic->data, req->sense, bytes))
>> err = -EFAULT;
>> }
>> - } else {
>> + } else if (scsi_result_is_good(req->result)) {
>> if (copy_to_user(sic->data, buffer, out_len))
>> err = -EFAULT;
>> }
>>
> Hmm. Not sure about this one.
> The prime motivator behind sg is to get _precisely_ all flags of the
> command, and not do in-kernel error handling.
> So one could argue that this behaviour is intentional, and would break
> existing use-cases.
>
Thanks for the review.
The existing usersapce can do nothing with the uninitialized data. Or
the driver or disk may fill some data and at the same time set host_byte
or driver_byte to non-zero? I'm not sure about this. And the return
value of sg_scsi_ioctl() just get the status byte(only 8 bit), how can
the users know about this situation?
Thanks,
Jason
> Doug?
>
> Cheers,
>
> Hannes
next prev parent reply other threads:[~2021-03-19 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 3:01 [PATCH 0/3] scsi: check the whole result in some places Jason Yan
2021-03-19 3:01 ` [PATCH 1/3] scsi: check the whole result for reading write protect flag Jason Yan
2021-03-19 7:55 ` Hannes Reinecke
2021-03-25 2:50 ` Martin K. Petersen
2021-03-27 6:57 ` Jason Yan
2021-03-19 3:01 ` [PATCH 2/3] scsi: only copy data to user when the whole result is good Jason Yan
2021-03-19 7:56 ` Hannes Reinecke
2021-03-19 8:22 ` Jason Yan [this message]
2021-03-19 3:01 ` [PATCH 3/3] scsi: switch to use scsi_result_is_good() in scsi_result_to_blk_status() Jason Yan
2021-03-19 7:56 ` Hannes Reinecke
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=ce784b08-b020-f67e-d902-a15affbdb1ca@huawei.com \
--to=yanaijie@huawei.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=kbusch@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.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;
as well as URLs for NNTP newsgroup(s).