mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "beanhuo@micron.com" <beanhuo@micron.com>,
	"James.Bottomley@HansenPartnership.com"
	<James.Bottomley@HansenPartnership.com>,
	"hongjiefang@asrmicro.com" <hongjiefang@asrmicro.com>,
	"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
	"avri.altman@wdc.com" <avri.altman@wdc.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"bvanassche@acm.org" <bvanassche@acm.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] scsi: ufs: core: handle PM commands timeout before SCSI EH
Date: Mon, 8 Jun 2026 08:51:37 +0000	[thread overview]
Message-ID: <46bca519aa91a71ffd2c322c2e7239b52541e134.camel@mediatek.com> (raw)
In-Reply-To: <20260605112034.3802540-1-hongjiefang@asrmicro.com>

On Fri, 2026-06-05 at 19:20 +0800, Hongjie Fang wrote:
> A PM START STOP sent from the UFS well-known LU resume path can race
> with
> SCSI EH.
> 
> The "wl resume" task flow is:
>   __ufshcd_wl_resume()
>     ufshcd_set_dev_pwr_mode(UFS_ACTIVE_PWR_MODE)
>       ufshcd_execute_start_stop()
>         scsi_execute_cmd()
>           blk_execute_rq           <-- wait
>           scsi_check_passthrough() <-- may retry START STOP
> 
> If the first START STOP time out, SCSI EH may already recover the
> link and
> reset the device before scsi_execute_cmd() returns:
>   scsi_timeout()
>     scsi_eh_scmd_add()
>       scsi_error_handler()
>         scsi_unjam_host()
>           scsi_eh_ready_devs()
>             scsi_eh_host_reset()
>               ufshcd_eh_host_reset_handler()
>                 if (hba->pm_op_in_progress)
>                   ufshcd_link_recovery()
>                     ufshcd_device_reset()
>                     ufshcd_host_reset_and_restore()
>           ...
>           scsi_eh_flush_done_q()   <-- wakeup "wl resume" task
>         ...                        <-- host still in SHOST_RECOVERY
>         scsi_restart_operations()
> 
> A later passthrough retry can then run while the host is still in
> SHOST_RECOVERY and hit the SCMD_FAIL_IF_RECOVERING path:
>   scsi_queue_rq()
>     if (scsi_host_in_recovery(shost) &&
>         cmd->flags & SCMD_FAIL_IF_RECOVERING)
>       return BLK_STS_OFFLINE
> 
> That retry completes with DID_ERROR or DID_NO_CONNECT even though EH
> may
> already have restored the device to an operational ACTIVE state.
> 
> Handle these PM timeouts directly from ufshcd_eh_timed_out() instead.
> After ufshcd_link_recovery(), complete the timed-out command
> immediately
> if it has not been completed already.
> 
> For regular SCSI commands, complete them with DID_REQUEUE to match
> the
> existing MCQ force-completion semantics and allow scsi_execute_cmd()
> to
> retry if needed. For reserved internal device-management commands,
> finish
> the request with DID_TIME_OUT without calling
> ufshcd_release_scsi_cmd()
> since those commands use different resource lifetime rules.
> 
> The system_suspending flag is no longer needed because PM command
> timeout
> handling now uses pm_op_in_progress.
> 
> Fixes: b8c3a7bac9b6 ("scsi: ufs: Have midlayer retry start stop
> errors")
> Signed-off-by: Hongjie Fang <hongjiefang@asrmicro.com>
> ---

Thanks for fix this bug.
Reviewed-by: Peter Wang <peter.wang@mediatek.com>

  parent reply	other threads:[~2026-06-08  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05 11:20 Hongjie Fang
2026-06-05 15:41 ` Bart Van Assche
2026-06-08  8:51 ` Peter Wang (王信友) [this message]
2026-06-08 21:42 ` Martin K. Petersen
2026-06-16  2:26 ` Martin K. Petersen

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=46bca519aa91a71ffd2c322c2e7239b52541e134.camel@mediatek.com \
    --to=peter.wang@mediatek.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=hongjiefang@asrmicro.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®