From: Hannes Reinecke <hare@suse.de>
To: Jason Yan <yanaijie@huawei.com>,
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 1/3] scsi: check the whole result for reading write protect flag
Date: Fri, 19 Mar 2021 08:55:02 +0100 [thread overview]
Message-ID: <078d47ac-907c-ec20-f600-7073bf375f1a@suse.de> (raw)
In-Reply-To: <20210319030128.1345061-2-yanaijie@huawei.com>
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 sd_read_write_protect_flag(),
> only status byte of the result is checked, we still consider the command
> returned good, and read sdkp->write_prot from the buffer. And because of
> bug [1], garbage data is copied to the buffer, the disk sometimes
> be set readonly. When the scsi device is set running again, users cannot
> write data to the disk.
>
> Fix this by check the whole result returned by the driver.
>
> [1] https://patchwork.kernel.org/project/linux-block/patch/20210318122621.330010-1-yanaijie@huawei.com/
>
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
> ---
> drivers/scsi/sd.c | 6 +++---
> include/scsi/scsi.h | 13 +++++++++++++
> 2 files changed, 16 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> index ed0b1bb99f08..16f8cd2895fd 100644
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -2669,18 +2669,18 @@ sd_read_write_protect_flag(struct scsi_disk *sdkp, unsigned char *buffer)
> * 5: Illegal Request, Sense Code 24: Invalid field in
> * CDB.
> */
> - if (!scsi_status_is_good(res))
> + if (!scsi_result_is_good(res))
> res = sd_do_mode_sense(sdkp, 0, 0, buffer, 4, &data, NULL);
>
> /*
> * Third attempt: ask 255 bytes, as we did earlier.
> */
> - if (!scsi_status_is_good(res))
> + if (!scsi_result_is_good(res))
> res = sd_do_mode_sense(sdkp, 0, 0x3F, buffer, 255,
> &data, NULL);
> }
>
> - if (!scsi_status_is_good(res)) {
> + if (!scsi_result_is_good(res)) {
> sd_first_printk(KERN_WARNING, sdkp,
> "Test WP failed, assume Write Enabled\n");
> } else {
> diff --git a/include/scsi/scsi.h b/include/scsi/scsi.h
> index e75cca25338a..db0f346a31b2 100644
> --- a/include/scsi/scsi.h
> +++ b/include/scsi/scsi.h
> @@ -55,6 +55,19 @@ static inline int scsi_status_is_good(int status)
> (status == SAM_STAT_COMMAND_TERMINATED));
> }
>
> +/** scsi_result_is_good - check the result return.
> + *
> + * @result: the result passed up from the driver (including host and
> + * driver components)
> + *
> + * Drivers may only set other bytes but not status byte.
> + * This checks both the status byte and other bytes.
> + */
> +static inline int scsi_result_is_good(int result)
> +{
> + return scsi_status_is_good(result) && (result & ~0xff) == 0;
> +}
> +
>
> /*
> * standard mode-select header prepended to all mode-select commands
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
next prev parent reply other threads:[~2021-03-19 7:55 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 [this message]
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
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=078d47ac-907c-ec20-f600-7073bf375f1a@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--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 \
--cc=yanaijie@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;
as well as URLs for NNTP newsgroup(s).