From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "bvanassche@acm.org" <bvanassche@acm.org>,
"hongjiefang@asrmicro.com" <hongjiefang@asrmicro.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] scsi: core: pair EH runtime PM get and put
Date: Mon, 3 Aug 2026 07:36:31 +0000 [thread overview]
Message-ID: <2cb29545a977497af17fe3ac5346b203d59b9bf3.camel@mediatek.com> (raw)
In-Reply-To: <20260729111614.2407559-1-hongjiefang@asrmicro.com>
On Wed, 2026-07-29 at 19:16 +0800, Hongjie Fang wrote
> shost->eh_noresume is currently consulted twice in one error handling
> iteration: once before scsi_autopm_get_host() and once again before
> scsi_autopm_put_host().
>
> That is racy when a PM-triggered error path flips shost->eh_noresume
> while
> the SCSI EH thread is still running.
>
> The problem flow looks like this:
> PM path
> ufshcd_set_dev_pwr_mode()
> shost->eh_noresume = 1
> ufshcd_execute_start_stop <-- trigger EH
> ...
> shost->eh_noresume = 0
>
> EH path
> scsi_error_handler()
> if (!shost->eh_noresume)
> scsi_autopm_get_host() <-- skipped
> ...
> if (!shost->eh_noresume)
> scsi_autopm_put_host() <-- executed later
>
> In that case one EH iteration can skip autoresume on entry and still
> drop
> a runtime PM reference on exit. That leaves an unmatched runtime PM
> put
> and can trigger a runtime PM usage count underflow.
>
> Fix this by making eh_noresume a regular bool so it can be accessed
> with
> READ_ONCE() and WRITE_ONCE(). Snapshot it once per EH iteration and
> use
> that snapshot for both runtime PM get and put decisions.
>
> Fixes: ae0751ffc77e ("[SCSI] add flag to skip the runtime PM calls on
> the host")
> Signed-off-by: Hongjie Fang <hongjiefang@asrmicro.com>
> ---
Reviewed-by: Peter Wang <peter.wang@mediatek.com>
prev parent reply other threads:[~2026-08-03 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 11:16 Hongjie Fang
2026-07-30 18:33 ` Bart Van Assche
2026-08-03 7:36 ` Peter Wang (王信友) [this message]
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=2cb29545a977497af17fe3ac5346b203d59b9bf3.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=avri.altman@wdc.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 \
--cc=stern@rowland.harvard.edu \
/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®