From: John Garry <john.garry@huawei.com>
To: Bart Van Assche <bvanassche@acm.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-scsi@vger.kernel.org>,
Ming Lei <ming.lei@redhat.com>, Hannes Reinecke <hare@suse.de>,
<ericspero@icloud.com>, <jason600.groome@gmail.com>
Subject: Re: [PATCH 3/3] scsi: sd: Rework asynchronous resume support
Date: Thu, 30 Jun 2022 17:23:36 +0100 [thread overview]
Message-ID: <82e30007-1ffc-92e4-38b5-eaf7dd2e316d@huawei.com> (raw)
In-Reply-To: <20220628222131.14780-4-bvanassche@acm.org>
On 28/06/2022 23:21, Bart Van Assche wrote:
> For some technologies, e.g. an ATA bus, resuming can take multiple
> seconds. Waiting for resume to finish can cause a very noticeable delay.
> Hence this patch that restores the behavior from before patch "scsi:
> core: pm: Rely on the device driver core for async power management" for
> most SCSI devices.
>
> This patch introduces a behavior change: if the START command fails, do
> not consider this as a SCSI disk resume failure.
>
> Cc: Ming Lei <ming.lei@redhat.com>
> Cc: Hannes Reinecke <hare@suse.de>
> Cc: John Garry <john.garry@huawei.com>
> Cc: ericspero@icloud.com
> Cc: jason600.groome@gmail.com
> Tested-by: jason600.groome@gmail.com
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=215880
> Fixes: a19a93e4c6a9 ("scsi: core: pm: Rely on the device driver core for async power management")
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
> drivers/scsi/sd.c | 79 ++++++++++++++++++++++++++++++++++++-----------
> drivers/scsi/sd.h | 5 +++
> 2 files changed, 66 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> index 895b56c8f25e..06888b675e71 100644
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -103,6 +103,7 @@ static void sd_config_discard(struct scsi_disk *, unsigned int);
> static void sd_config_write_same(struct scsi_disk *);
> static int sd_revalidate_disk(struct gendisk *);
> static void sd_unlock_native_capacity(struct gendisk *disk);
> +static void sd_start_done_work(struct work_struct *work);
> static int sd_probe(struct device *);
> static int sd_remove(struct device *);
> static void sd_shutdown(struct device *);
> @@ -3463,6 +3464,7 @@ static int sd_probe(struct device *dev)
> sdkp->max_retries = SD_MAX_RETRIES;
> atomic_set(&sdkp->openers, 0);
> atomic_set(&sdkp->device->ioerr_cnt, 0);
> + INIT_WORK(&sdkp->start_done_work, sd_start_done_work);
>
> if (!sdp->request_queue->rq_timeout) {
> if (sdp->type != TYPE_MOD)
> @@ -3585,12 +3587,64 @@ static void scsi_disk_release(struct device *dev)
> kfree(sdkp);
> }
>
> +/* Process sense data after a START command finished. */
> +static void sd_start_done_work(struct work_struct *work)
> +{
> + struct scsi_disk *sdkp = container_of(work, typeof(*sdkp),
> + start_done_work);
> + struct scsi_sense_hdr sshdr;
> + int res = sdkp->start_result;
> +
> + if (res == 0)
> + return;
> +
> + sd_print_result(sdkp, "Start/Stop Unit failed", res);
> + if (res > 0 && scsi_normalize_sense(sdkp->start_sense_buffer,
> + sdkp->start_sense_len, &sshdr))
> + sd_print_sense_hdr(sdkp, &sshdr);
nit: maybe you can reduce indentation, like:
if (res < 0)
return;
if (scsi_normalize_sense(sdkp->start_sense_buffer,
sdkp->start_sense_len, &sshdr)) {
sd_print_sense_hdr(sdkp, &sshdr);
}
> +}
> +
> +/* A START command finished. May be called from interrupt context. */
> +static void sd_start_done(struct request *req, blk_status_t status)
> +{
> + const struct scsi_cmnd *scmd = blk_mq_rq_to_pdu(req);
> + struct scsi_disk *sdkp = scsi_disk(req->q->disk);
> +
> + sdkp->start_result = scmd->result;
> + WARN_ON_ONCE(scmd->sense_len > SCSI_SENSE_BUFFERSIZE);
If scmd->sense_len > SCSI_SENSE_BUFFERSIZE, do you really want to go on
to copy at sdkp->start_sense_buffer (which is of size
SCSI_SENSE_BUFFERSIZE)? Won't that cause a corruption?
> + sdkp->start_sense_len = scmd->sense_len;
> + memcpy(sdkp->start_sense_buffer, scmd->sense_buffer, scmd->sense_len);
> + WARN_ON_ONCE(!schedule_work(&sdkp->start_done_work));
> +}
> +
> +/* Submit a START command asynchronously. */
> +static int sd_submit_start(struct scsi_disk *sdkp, u8 cmd[], u8 cmd_len)
> +{
> + struct scsi_device *sdev = sdkp->device;
> + struct request_queue *q = sdev->request_queue;
> + struct request *req;
> + struct scsi_cmnd *scmd;
> +
> + req = scsi_alloc_request(q, REQ_OP_DRV_IN, BLK_MQ_REQ_PM);
> + if (IS_ERR(req))
> + return PTR_ERR(req);
> +
> + scmd = blk_mq_rq_to_pdu(req);
> + scmd->cmd_len = cmd_len;
> + memcpy(scmd->cmnd, cmd, cmd_len);
> + scmd->allowed = sdkp->max_retries;
> + req->timeout = SD_TIMEOUT;
> + req->rq_flags |= RQF_PM | RQF_QUIET;
> + req->end_io = sd_start_done;
> + blk_execute_rq_nowait(req, /*at_head=*/true);
> +
> + return 0;
> +}
> +
> static int sd_start_stop_device(struct scsi_disk *sdkp, int start)
> {
> unsigned char cmd[6] = { START_STOP }; /* START_VALID */
> - struct scsi_sense_hdr sshdr;
> struct scsi_device *sdp = sdkp->device;
> - int res;
>
> if (start)
> cmd[4] |= 1; /* START */
> @@ -3601,23 +3655,10 @@ static int sd_start_stop_device(struct scsi_disk *sdkp, int start)
> if (!scsi_device_online(sdp))
> return -ENODEV;
>
> - res = scsi_execute(sdp, cmd, DMA_NONE, NULL, 0, NULL, &sshdr,
> - SD_TIMEOUT, sdkp->max_retries, 0, RQF_PM, NULL);
> - if (res) {
> - sd_print_result(sdkp, "Start/Stop Unit failed", res);
> - if (res > 0 && scsi_sense_valid(&sshdr)) {
> - sd_print_sense_hdr(sdkp, &sshdr);
> - /* 0x3a is medium not present */
> - if (sshdr.asc == 0x3a)
> - res = 0;
> - }
> - }
> + /* Wait until processing of sense data has finished. */
> + flush_work(&sdkp->start_done_work);
>
> - /* SCSI error codes must not go to the generic layer */
> - if (res)
> - return -EIO;
> -
> - return 0;
> + return sd_submit_start(sdkp, cmd, sizeof(cmd));
> }
>
> /*
> @@ -3644,6 +3685,8 @@ static void sd_shutdown(struct device *dev)
> sd_printk(KERN_NOTICE, sdkp, "Stopping disk\n");
> sd_start_stop_device(sdkp, 0);
> }
> +
> + flush_work(&sdkp->start_done_work);
> }
>
> static int sd_suspend_common(struct device *dev, bool ignore_stop_errors)
> diff --git a/drivers/scsi/sd.h b/drivers/scsi/sd.h
> index 5eea762f84d1..b89187761d61 100644
> --- a/drivers/scsi/sd.h
> +++ b/drivers/scsi/sd.h
> @@ -150,6 +150,11 @@ struct scsi_disk {
> unsigned urswrz : 1;
> unsigned security : 1;
> unsigned ignore_medium_access_errors : 1;
> +
> + int start_result;
> + u32 start_sense_len;
> + u8 start_sense_buffer[SCSI_SENSE_BUFFERSIZE];
> + struct work_struct start_done_work;
> };
> #define to_scsi_disk(obj) container_of(obj, struct scsi_disk, disk_dev)
>
> .
next prev parent reply other threads:[~2022-06-30 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 22:21 [PATCH 0/3] Reduce ATA disk resume time Bart Van Assche
2022-06-28 22:21 ` [PATCH 1/3] scsi: core: Move the definition of SCSI_QUEUE_DELAY Bart Van Assche
2022-06-28 22:21 ` [PATCH 2/3] scsi: core: Retry after a delay if the device is becoming ready Bart Van Assche
2022-06-29 1:21 ` Ming Lei
2022-06-29 22:06 ` Bart Van Assche
2022-06-28 22:21 ` [PATCH 3/3] scsi: sd: Rework asynchronous resume support Bart Van Assche
2022-06-29 6:02 ` Hannes Reinecke
2022-06-30 16:09 ` Bart Van Assche
2022-06-30 16:23 ` John Garry [this message]
2022-06-30 18:57 ` Bart Van Assche
2022-06-30 19:28 ` Bart Van Assche
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=82e30007-1ffc-92e4-38b5-eaf7dd2e316d@huawei.com \
--to=john.garry@huawei.com \
--cc=bvanassche@acm.org \
--cc=ericspero@icloud.com \
--cc=hare@suse.de \
--cc=jaegeuk@kernel.org \
--cc=jason600.groome@gmail.com \
--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).