mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Block <bblock@linux.ibm.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
	acelan.kao@canonical.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: core: Avoid doing rescan on suspended device
Date: Thu, 20 Apr 2023 17:43:21 +0000	[thread overview]
Message-ID: <20230420174321.GA123094@t480-pf1aa2c2> (raw)
In-Reply-To: <20230419054112.269734-1-kai.heng.feng@canonical.com>

On Wed, Apr 19, 2023 at 01:41:12PM +0800, Kai-Heng Feng wrote:
> During system resume, if an EH is schduled after ATA host is resumed
> (i.e. ATA_PFLAG_PM_PENDING cleared), but before the disk device is
> resumed, the device_lock hold by scsi_rescan_device() is never released
> so the dpm_resume() of the disk is blocked forerver.
> 
> That's because scsi_attach_vpd() is expecting the disk device is in
> operational state, as it doesn't work on suspended device.
> 
> To avoid such deadlock, avoid doing rescan if the disk is still
> suspended so the resume process of the disk device can proceed.

I'm no expert on suspend/resume, but wouldn't you then potentially miss
changes that have been done to the LUN during suspend?

What takes care of updating the VPDs, scsi-disk re-evaluation and such
in this case, when you block it initially during wakeup?

> 
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ---
>  drivers/scsi/scsi_scan.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
> index d217be323cc6..36680cb1535b 100644
> --- a/drivers/scsi/scsi_scan.c
> +++ b/drivers/scsi/scsi_scan.c
> @@ -1621,6 +1621,9 @@ void scsi_rescan_device(struct device *dev)
>  {
>  	struct scsi_device *sdev = to_scsi_device(dev);
>  
> +	if (dev->power.is_prepared)
> +		return;
> +
>  	device_lock(dev);
>  
>  	scsi_attach_vpd(sdev);
> -- 
> 2.34.1
> 

-- 
Best Regards, Benjamin Block        /        Linux on IBM Z Kernel Development
IBM Deutschland Research & Development GmbH    /   https://www.ibm.com/privacy
Vors. Aufs.-R.: Gregor Pillen         /         Geschäftsführung: David Faller
Sitz der Ges.: Böblingen     /    Registergericht: AmtsG Stuttgart, HRB 243294

  reply	other threads:[~2023-04-20 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19  5:41 Kai-Heng Feng
2023-04-20 17:43 ` Benjamin Block [this message]
2023-04-24  3:30   ` Kai-Heng Feng

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=20230420174321.GA123094@t480-pf1aa2c2 \
    --to=bblock@linux.ibm.com \
    --cc=acelan.kao@canonical.com \
    --cc=jejb@linux.ibm.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®