From: John Garry <john.garry@huawei.com>
To: Bart Van Assche <bvanassche@acm.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Hannes Reinecke <hare@suse.de>,
"Geert Uytterhoeven" <geert@linux-m68k.org>, <gzhqyz@gmail.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>
Subject: Re: [PATCH] scsi: sd: Revert "Rework asynchronous resume support"
Date: Tue, 16 Aug 2022 19:00:38 +0100 [thread overview]
Message-ID: <8a83665a-1951-a326-f930-8fcbb0c4dd9a@huawei.com> (raw)
In-Reply-To: <20220816172638.538734-1-bvanassche@acm.org>
On 16/08/2022 18:26, Bart Van Assche wrote:
> Although patch "Rework asynchronous resume support" eliminates the delay
> for some ATA disks after resume, it causes resume of ATA disks to fail
> on other setups. See also:
> * "Resume process hangs for 5-6 seconds starting sometime in 5.16"
> (https://bugzilla.kernel.org/show_bug.cgi?id=215880).
> * Geert's regression report
> (https://lore.kernel.org/linux-scsi/alpine.DEB.2.22.394.2207191125130.1006766@ramsan.of.borg/).
>
> This is what I understand about this issue:
> * During resume, ata_port_pm_resume() starts the SCSI error handler.
> This changes the SCSI host state into SHOST_RECOVERY and causes
> scsi_queue_rq() to return BLK_STS_RESOURCE.
> * sd_resume() calls sd_start_stop_device() for ATA devices. That
> function in turn calls sd_submit_start() which tries to submit a START
> STOP UNIT command. That command can only be submitted after the SCSI
> error handler has changed the SCSI host state back to SHOST_RUNNING.
> * The SCSI error handler runs on its own thread and calls
> schedule_work(&(ap->scsi_rescan_task)). That causes
> ata_scsi_dev_rescan() to be called from the context of a kernel
> workqueue. That call hangs in blk_mq_get_tag(). I'm not sure why -
> maybe because all available tags have been allocated by
> sd_submit_start() calls (this is a guess).
>
> Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>
> Cc: Hannes Reinecke <hare@suse.de>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: gzhqyz@gmail.com
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Reported-by: gzhqyz@gmail.com
> Fixes: 88f1669019bd ("scsi: sd: Rework asynchronous resume support"; v6.0-rc1~114^2~68)
JFYI, Just now I see that 88f1669019bd also causes me issues for my SATA
disk:
root@(none)$ echo 0 > sys/class/sas_phy/phy-0:0:2/enable
[58.271646] sas: ex 500e004aaaaaaa1f phy02 change count has changed
[58.305876] sd 0:0:1:0: [sdb] Synchronizing SCSI cache
[58.305898] sd 0:0:1:0: [sdb] Synchronize Cache(10) failed: Result:
hostbyte=0x04 driverbyte=DRIVER_OK
[58.305901] sd 0:0:1:0: [sdb] Stopping disk
[58.305911] sd 0:0:1:0: [sdb] Start/Stop Unit failed: Result:
hostbyte=0x04 driverbyte=DRIVER_OK
root@(none)$ echo 1 > sys/class/sas_phy/phy-0:0:2/enable
[95.405836] INFO: task kworker/u128:0:8 blocked for more than 30 seconds.
[95.412618] Not tainted 5.19.0-rc1-00128-g88f1669019bd-dirty #1166
[95.419311] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[95.427130] task:kworker/u128:0 state:D stack: 0 pid: 8 ppid: 2
flags:0x00000008
[95.435475] Workqueue: HISI0162:01_event_q sas_port_event_worker
[95.441481] Call trace:
[95.443918] __switch_to+0x11c/0x1a8
[95.447491] __schedule+0x264/0x718
[95.450972] schedule+0x50/0xc8
[95.454106] schedule_timeout+0x19c/0x250
[95.458108] wait_for_completion+0x84/0x140
[95.462283] flush_workqueue+0xfc/0x3d0
[95.466114] sas_porte_broadcast_rcvd+0x5c/0x68
[95.470638] sas_port_event_worker+0x2c/0x50
[95.474899] process_one_work+0x1e4/0x348
[95.478901] worker_thread+0x48/0x418
[95.482555] kthread+0xf4/0x110
[95.485687] ret_from_fork+0x10/0x20
[95.489274] INFO: task kworker/u128:1:462 blocked for more than 30 seconds.
[95.496226] Not tainted 5.19.0-rc1-00128-g88f1669019bd-dirty #1166
[95.502918] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[95.510736] task:kworker/u128:1 state:D stack: 0 pid: 462 ppid: 2
flags:0x00000008
[95.519080] Workqueue: HISI0162:01_disco_q sas_revalidate_domain
[95.525080] Call trace:
[95.527517] __switch_to+0x11c/0x1a8
[95.531085] __schedule+0x264/0x718
[95.534565] schedule+0x50/0xc8
[95.537694] blk_mq_freeze_queue_wait+0x7c/0xb0
[95.542218] blk_mq_freeze_queue+0x1c/0x28
[95.546307] disk_release+0x40/0xf0
[95.549784] device_release+0x30/0x90
[95.553441] kobject_put+0x90/0x108
[95.556923] put_device+0x10/0x20
[95.560231] put_disk+0x18/0x28
[95.563363] sd_remove+0x44/0x58
[95.566585] device_remove+0x6c/0x78
[95.570153] device_release_driver_internal+0xd8/0x180
[95.575284] device_release_driver+0x14/0x20
[95.579545] bus_remove_device+0xc8/0x108
[95.583547] device_del+0x16c/0x3a0
[95.587028] __scsi_remove_device+0xf0/0x130
[95.591290] scsi_remove_device+0x28/0x40
[95.595291] scsi_remove_target+0x1b8/0x220
[95.599466] sas_rphy_remove+0x5c/0x60
[95.603208] sas_rphy_delete+0x14/0x28
[95.606949] sas_destruct_devices+0x54/0x88
[95.611124] sas_revalidate_domain+0x60/0x148
[95.615472] process_one_work+0x1e4/0x348
[95.619474] worker_thread+0x48/0x418
[95.623129] kthread+0xf4/0x110
[95.626261] ret_from_fork+0x10/0x20
[95.629830] INFO: task sh:541 blocked for more than 30 seconds.
[95.635740] Not tainted 5.19.0-rc1-00128-g88f1669019bd-dirty #1166
[95.642431] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[95.650250] task:sh state:D stack: 0 pid: 541 ppid: 1 flags:0x00000000
[95.658594] Call trace:
[95.661028] __switch_to+0x11c/0x1a8
[95.664597] __schedule+0x264/0x718
[95.668076] schedule+0x50/0xc8
[95.671210] schedule_timeout+0x19c/0x250
[95.675211] wait_for_completion+0x84/0x140
[95.679387] flush_workqueue+0xfc/0x3d0
[95.683214] drain_workqueue+0xb0/0x158
[95.687043] __sas_drain_work+0x3c/0x98
[95.690870] sas_drain_work+0x58/0x60
[95.694524] queue_phy_enable+0x84/0xc8
[95.698352] do_sas_phy_enable.isra.7+0x58/0xb0
[95.702875] store_sas_phy_enable+0x48/0x78
[95.707051] dev_attr_store+0x14/0x28
[95.710706] sysfs_kf_write+0x48/0x58
[95.714362] kernfs_fop_write_iter+0x118/0x1a0
[95.718798] new_sync_write+0xdc/0x168
[95.722543] vfs_write+0x1b8/0x388
[95.725938] ksys_write+0x64/0xf0
[95.729241] __arm64_sys_write+0x14/0x20
[95.733157] invoke_syscall+0x40/0xf8
[95.736814] el0_svc_common.constprop.3+0x6c/0xf8
[95.741511] do_el0_svc+0x28/0xc8
[95.744818] el0_svc+0x28/0x80
[95.747865] el0t_64_sync_handler+0x94/0xb8
[95.752039] el0t_64_sync+0x178/0x17c
BTW, I see 88f1669019bd is queued for stable...
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
> drivers/scsi/sd.c | 84 ++++++++++-------------------------------------
> drivers/scsi/sd.h | 5 ---
> 2 files changed, 18 insertions(+), 71 deletions(-)
>
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> index 8f79fa6318fe..eb76ba055021 100644
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -103,7 +103,6 @@ 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 *);
> @@ -3471,7 +3470,6 @@ 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)
> @@ -3594,69 +3592,12 @@ 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)
> - 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);
> - sdkp->start_sense_len = scmd->sense_len;
> - memcpy(sdkp->start_sense_buffer, scmd->sense_buffer,
> - ARRAY_SIZE(sdkp->start_sense_buffer));
> - 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 */
> @@ -3667,10 +3608,23 @@ static int sd_start_stop_device(struct scsi_disk *sdkp, int start)
> if (!scsi_device_online(sdp))
> return -ENODEV;
>
> - /* Wait until processing of sense data has finished. */
> - flush_work(&sdkp->start_done_work);
> + 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;
> + }
> + }
>
> - return sd_submit_start(sdkp, cmd, sizeof(cmd));
> + /* SCSI error codes must not go to the generic layer */
> + if (res)
> + return -EIO;
> +
> + return 0;
> }
>
> /*
> @@ -3697,8 +3651,6 @@ 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 b89187761d61..5eea762f84d1 100644
> --- a/drivers/scsi/sd.h
> +++ b/drivers/scsi/sd.h
> @@ -150,11 +150,6 @@ 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-08-16 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 17:26 [PATCH] scsi: sd: Revert "Rework asynchronous resume support" Bart Van Assche
2022-08-16 18:00 ` John Garry [this message]
2022-08-16 18:06 ` Bart Van Assche
2022-08-17 8:20 ` John Garry
2022-08-17 20:06 ` Vlastimil Babka
2022-08-22 20:53 ` Vlastimil Babka
2022-08-20 15:37 ` Hans de Goede
2022-08-21 9:16 ` Geert Uytterhoeven
2022-08-22 2:52 ` Bart Van Assche
2022-08-23 6:41 ` Geert Uytterhoeven
2022-08-23 18:10 ` Bart Van Assche
2022-08-26 7:54 ` Geert Uytterhoeven
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=8a83665a-1951-a326-f930-8fcbb0c4dd9a@huawei.com \
--to=john.garry@huawei.com \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=geert@linux-m68k.org \
--cc=gzhqyz@gmail.com \
--cc=hare@suse.de \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).