[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <491d53b9-a110-431b-9a5e-3b46d833fdbb@acm.org>
Date: Thu, 29 Jan 2026 09:04:36 -0800
From: Bart Van Assche <bvanassche@....org>
To: Thomas Yen <thomasyen@...gle.com>
Cc: Stable Tree <stable@...r.kernel.org>,
Alim Akhtar <alim.akhtar@...sung.com>, Avri Altman <avri.altman@....com>,
"James E.J. Bottomley" <James.Bottomley@...senPartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Peter Wang <peter.wang@...iatek.com>, Bean Huo <beanhuo@...ron.com>,
Adrian Hunter <adrian.hunter@...el.com>,
"Bao D. Nguyen" <quic_nguyenb@...cinc.com>,
"open list:UNIVERSAL FLASH STORAGE HOST CONTROLLER DRIVER"
<linux-scsi@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/1] scsi: ufs: core: Flush exception handling work
when RPM level is zero
On 1/28/26 11:06 PM, Thomas Yen wrote:
> Ensure that the exception event handling work is explicitly flushed
> during suspend when the runtime power management level is set to
> UFS_PM_LVL_0.
>
> When the RPM level is zero, the device power mode and link state both
> remain active. Previously, the UFS core driver bypassed flushing
> exception event handling jobs in this configuration. This created a race
> condition where the driver could attempt to access the host controller
> to handle an exception after the system had already entered a deep
> power-down state, resulting in a system crash.
>
> Explicitly flush this work and disable auto BKOPs before the suspend
> callback proceeds. This guarantees that pending exception tasks complete
> and prevents illegal hardware access during the power-down sequence.
>
> Signed-off-by: Thomas Yen <thomasyen@...gle.com>
> Cc: Stable Tree <stable@...r.kernel.org>
For future patch submissions, please place the Cc: tag above the
Signed-off-by tag. I think that is a widely used convention in the Linux
kernel community. Anyway:
Reviewed-by: Bart Van Assche <bvanassche@....org>
Powered by blists - more mailing lists