From: Damien Le Moal <dlemoal@kernel.org>
To: Hannes Reinecke <hare@suse.de>, 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>
Subject: Re: [PATCH 02/19] ata: libata-core: Fix port and device removal
Date: Mon, 11 Sep 2023 15:44:15 +0900 [thread overview]
Message-ID: <db4e461c-d797-fb76-7d97-e38d3640de89@kernel.org> (raw)
In-Reply-To: <add77796-ff0f-4311-8c4d-6597695e89ed@suse.de>
On 9/11/23 15:37, Hannes Reinecke wrote:
> On 9/11/23 06:02, Damien Le Moal wrote:
>> Whenever an ATA adapter driver is removed (e.g. rmmod),
>> ata_port_detach() is called repeatedly for all the adapter ports to
>> remove (unload) the devices attached to the port and delete the port
>> device itself. Removing of devices is done using libata EH with the
>> ATA_PFLAG_UNLOADING port flag set. This causes libata EH to execute
>> ata_eh_unload() which disables all devices attached to the port.
>>
>> ata_port_detach() finishes by calling scsi_remove_host() to remove the
>> scsi host associated with the port. This function will trigger the
>> removal of all scsi devices attached to the host and in the case of
>> disks, calls to sd_shutdown() which will flush the device write cache
>> and stop the device. However, given that the devices were already
>> disabled by ata_eh_unload(), the synchronize write cache command and
>> start stop unit commands fail. E.g. running "rmmod ahci" with first
>> removing sd_mod results in error messages like:
>>
>> ata13.00: disable device
>> sd 0:0:0:0: [sda] Synchronizing SCSI cache
>> sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result:
>> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
>> sd 0:0:0:0: [sda] Stopping disk
>> sd 0:0:0:0: [sda] Start/Stop Unit failed: Result: hostbyte=DID_BAD_TARGET
>> driverbyte=DRIVER_OK
>>
>> Fix this by removing all scsi devices of the ata devices connected to
>> the port before scheduling libata EH to disable the ATA devices.
>>
>> Fixes: 720ba12620ee ("[PATCH] libata-hp: update unload-unplug")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
>> ---
>> drivers/ata/libata-core.c | 21 ++++++++++++++++++++-
>> 1 file changed, 20 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
>> index c4898483d716..693cb3cd70cd 100644
>> --- a/drivers/ata/libata-core.c
>> +++ b/drivers/ata/libata-core.c
>> @@ -5952,11 +5952,30 @@ static void ata_port_detach(struct ata_port *ap)
>> struct ata_link *link;
>> struct ata_device *dev;
>> - /* tell EH we're leaving & flush EH */
>> + /* Wait for any ongoing EH */
>> + ata_port_wait_eh(ap);
>> +
>> + mutex_lock(&ap->scsi_scan_mutex);
>> spin_lock_irqsave(ap->lock, flags);
>> +
>> + /* Remove scsi devices */
>> + ata_for_each_link(link, ap, HOST_FIRST) {
>> + ata_for_each_dev(dev, link, ALL) {
>> + if (dev->sdev) {
>> + spin_unlock_irqrestore(ap->lock, flags);
>> + scsi_remove_device(dev->sdev);
>> + spin_lock_irqsave(ap->lock, flags);
>> + dev->sdev = NULL;
>> + }
>> + }
>> + }
>> +
>> + /* Tell EH to disable all devices */
>> ap->pflags |= ATA_PFLAG_UNLOADING;
>> ata_port_schedule_eh(ap);
>> +
>> spin_unlock_irqrestore(ap->lock, flags);
>> + mutex_unlock(&ap->scsi_scan_mutex);
>>
> Are you sure about releasing scan_mutex after ata_port_schedule_eh()?
> Technically ata_port_schedule_eh() will be calling into SCSI rescan, which
> would take scan_mutex ...
> Not that it matter much, seeing that we've disconnected all devices, but still ...
UNLOADING is set and in that case, EH does nothing else than removing the
devices. So I think this is OK.
>
> Cheers,
>
> Hannes
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-09-11 6:44 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 4:01 [PATCH 00/19] Fix libata suspend/resume handling and code cleanup Damien Le Moal
2023-09-11 4:01 ` [PATCH 01/19] ata: libata-core: Fix ata_port_request_pm() locking Damien Le Moal
2023-09-11 6:34 ` Hannes Reinecke
2023-09-13 1:41 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 02/19] ata: libata-core: Fix port and device removal Damien Le Moal
2023-09-11 6:37 ` Hannes Reinecke
2023-09-11 6:44 ` Damien Le Moal [this message]
2023-09-11 7:07 ` Hannes Reinecke
2023-09-13 1:43 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 03/19] ata: libata-scsi: link ata port and scsi device Damien Le Moal
2023-09-11 6:41 ` Hannes Reinecke
2023-09-11 6:48 ` Damien Le Moal
2023-09-11 7:07 ` Hannes Reinecke
2023-09-11 10:38 ` John Garry
2023-09-11 11:48 ` Damien Le Moal
2023-09-11 15:15 ` John Garry
2023-09-12 6:13 ` Damien Le Moal
2023-09-12 8:49 ` John Garry
2023-09-12 9:00 ` Damien Le Moal
2023-09-12 9:19 ` John Garry
2023-09-13 1:43 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 04/19] ata: libata-scsi: Disable scsi device manage_start_stop Damien Le Moal
2023-09-11 6:46 ` Hannes Reinecke
2023-09-11 6:59 ` Damien Le Moal
2023-09-11 7:09 ` Hannes Reinecke
2023-09-14 16:37 ` Phillip Susi
2023-09-13 1:44 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 05/19] ata: libata-scsi: Fix delayed scsi_rescan_device() execution Damien Le Moal
2023-09-11 6:47 ` Hannes Reinecke
2023-09-13 1:44 ` Chia-Lin Kao (AceLan)
2023-09-14 17:25 ` Bart Van Assche
2023-09-14 22:05 ` Damien Le Moal
2023-09-11 4:02 ` [PATCH 06/19] ata: libata-core: Do not register PM operations for SAS ports Damien Le Moal
2023-09-11 6:50 ` Hannes Reinecke
2023-09-13 1:44 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 07/19] scsi: sd: Do not issue commands to suspended disks on remove Damien Le Moal
2023-09-11 6:51 ` Hannes Reinecke
2023-09-13 1:45 ` Chia-Lin Kao (AceLan)
2023-09-13 20:50 ` Bart Van Assche
2023-09-14 0:29 ` Damien Le Moal
2023-09-14 14:39 ` Bart Van Assche
2023-09-11 4:02 ` [PATCH 08/19] scsi: Remove scsi device no_start_on_resume flag Damien Le Moal
2023-09-11 6:52 ` Hannes Reinecke
2023-09-13 1:45 ` Chia-Lin Kao (AceLan)
2023-09-14 17:29 ` Bart Van Assche
2023-09-11 4:02 ` [PATCH 09/19] ata: libata-scsi: Cleanup ata_scsi_start_stop_xlat() Damien Le Moal
2023-09-11 6:57 ` Hannes Reinecke
2023-09-13 1:46 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 10/19] ata: libata-core: Synchronize ata_port_detach() with hotplug Damien Le Moal
2023-09-11 6:58 ` Hannes Reinecke
2023-09-13 1:46 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 11/19] ata: libata-core: Detach a port devices on shutdown Damien Le Moal
2023-09-11 6:59 ` Hannes Reinecke
2023-09-13 1:46 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 12/19] ata: libata-core: Remove ata_port_suspend_async() Damien Le Moal
2023-09-11 7:00 ` Hannes Reinecke
2023-09-13 1:47 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 13/19] ata: libata-core: Remove ata_port_resume_async() Damien Le Moal
2023-09-11 7:00 ` Hannes Reinecke
2023-09-13 1:47 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 14/19] ata: libata-core: skip poweroff for devices that are runtime suspended Damien Le Moal
2023-09-11 7:01 ` Hannes Reinecke
2023-09-13 1:48 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 15/19] ata: libata-core: Do not resume ports that have been " Damien Le Moal
2023-09-11 7:01 ` Hannes Reinecke
2023-09-13 1:48 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 16/19] ata: libata-sata: Improve ata_sas_slave_configure() Damien Le Moal
2023-09-11 7:02 ` Hannes Reinecke
2023-09-13 1:48 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 17/19] ata: libata-eh: Improve reset error messages Damien Le Moal
2023-09-11 7:03 ` Hannes Reinecke
2023-09-11 10:03 ` John Garry
2023-09-13 1:49 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 18/19] ata: libata-eh: Reduce "disable device" message verbosity Damien Le Moal
2023-09-11 7:05 ` Hannes Reinecke
2023-09-11 10:14 ` Sergei Shtylyov
2023-09-13 1:49 ` Chia-Lin Kao (AceLan)
2023-09-11 4:02 ` [PATCH 19/19] ata: libata: Cleanup inline DMA helper functions Damien Le Moal
2023-09-11 7:06 ` Hannes Reinecke
2023-09-13 1:49 ` Chia-Lin Kao (AceLan)
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=db4e461c-d797-fb76-7d97-e38d3640de89@kernel.org \
--to=dlemoal@kernel.org \
--cc=hare@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.