From: Bart Van Assche <bvanassche@acm.org>
To: Damien Le Moal <dlemoal@kernel.org>, linux-ide@vger.kernel.org
Cc: linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
John Garry <john.g.garry@oracle.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Paul Ausbeck <paula@soe.ucsc.edu>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Joe Breuer <linux-kernel@jmbreuer.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Chia-Lin Kao <acelan.kao@canonical.com>
Subject: Re: [PATCH v4 09/23] scsi: sd: Do not issue commands to suspended disks on shutdown
Date: Thu, 21 Sep 2023 14:36:01 -0700 [thread overview]
Message-ID: <daa44a6b-59fd-4735-b881-7d182a7d2a41@acm.org> (raw)
In-Reply-To: <20230920135439.929695-10-dlemoal@kernel.org>
On 9/20/23 06:54, Damien Le Moal wrote:
> If an error occurs when resuming a host adapter before the devices
> attached to the adapter are resumed, the adapter low level driver may
> remove the scsi host, resulting in a call to sd_remove() for the
> disks of the host. This in turn results in a call to sd_shutdown() which
> will issue a synchronize cache command and a start stop unit command to
> spindown the disk. sd_shutdown() issues the commands only if the device
> is not already suspended but does not check the power state for
> system-wide suspend/resume. That is, the commands may be issued with the
> device in a suspended state, which causes PM resume to hang, forcing a
> reset of the machine to recover.
>
> Fix this by not calling sd_shutdown() in sd_remove() if the device
> is not running.
Hi Damien,
I'd like to look into an alternative fix (after this patch series went
in) but I couldn't identify the call chain in the ATA resume code that
results in removal of the SCSI host. Can you please show me the call
chain that results in SCSI host removal if resuming fails?
Thanks,
Bart.
next prev parent reply other threads:[~2023-09-21 21:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 13:54 [PATCH v4 00/23] Fix libata suspend/resume handling and code cleanup Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 01/23] ata: libata-core: Fix ata_port_request_pm() locking Damien Le Moal
2023-09-20 18:54 ` Niklas Cassel
2023-09-20 13:54 ` [PATCH v4 02/23] ata: libata-core: Fix port and device removal Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 03/23] ata: libata-scsi: link ata port and scsi device Damien Le Moal
2023-09-20 18:55 ` Niklas Cassel
2023-09-21 14:16 ` John Garry
2023-09-21 17:30 ` Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 04/23] scsi: sd: Differentiate system and runtime start/stop management Damien Le Moal
2023-09-21 21:45 ` Bart Van Assche
2023-09-22 17:00 ` Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 05/23] ata: libata-scsi: Disable scsi device manage_system_start_stop Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 06/23] scsi: Do not attempt to rescan suspended devices Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 07/23] ata: libata-scsi: Fix delayed scsi_rescan_device() execution Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 08/23] ata: libata-core: Do not register PM operations for SAS ports Damien Le Moal
2023-09-21 14:01 ` John Garry
2023-09-20 13:54 ` [PATCH v4 09/23] scsi: sd: Do not issue commands to suspended disks on shutdown Damien Le Moal
2023-09-21 21:36 ` Bart Van Assche [this message]
2023-09-21 22:06 ` Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 10/23] ata: libata-core: Fix compilation warning in ata_dev_config_ncq() Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 11/23] ata: libata-eh: Fix compilation warning in ata_eh_link_report() Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 12/23] scsi: Remove scsi device no_start_on_resume flag Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 13/23] ata: libata-scsi: Cleanup ata_scsi_start_stop_xlat() Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 14/23] ata: libata-core: Synchronize ata_port_detach() with hotplug Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 15/23] ata: libata-core: Detach a port devices on shutdown Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 16/23] ata: libata-core: Remove ata_port_suspend_async() Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 17/23] ata: libata-core: Remove ata_port_resume_async() Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 18/23] ata: libata-core: Do not poweroff runtime suspended ports Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 19/23] ata: libata-core: Do not resume " Damien Le Moal
2023-09-21 7:32 ` Sergey Shtylyov
2023-09-21 17:31 ` Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 20/23] ata: libata-sata: Improve ata_sas_slave_configure() Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 21/23] ata: libata-eh: Improve reset error messages Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 22/23] ata: libata-eh: Reduce "disable device" message verbosity Damien Le Moal
2023-09-20 13:54 ` [PATCH v4 23/23] ata: libata: Cleanup inline DMA helper functions Damien Le Moal
2023-09-21 9:21 ` [PATCH v4 00/23] Fix libata suspend/resume handling and code cleanup Geert Uytterhoeven
2023-09-21 9:22 ` Geert Uytterhoeven
2023-09-21 17:30 ` Damien Le Moal
2023-09-21 19:53 ` Damien Le Moal
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=daa44a6b-59fd-4735-b881-7d182a7d2a41@acm.org \
--to=bvanassche@acm.org \
--cc=acelan.kao@canonical.com \
--cc=dlemoal@kernel.org \
--cc=geert@linux-m68k.org \
--cc=john.g.garry@oracle.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@jmbreuer.net \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=paula@soe.ucsc.edu \
--cc=rodrigo.vivi@intel.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