linux-kernel - Re: [PATCH 1/1] scsi: ufs: core: Fix EH failure after wlun resume error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7d964e31162bf93f583e6e78a3044152894ecb94.camel@mediatek.com>
Date: Wed, 12 Nov 2025 08:17:26 +0000
From: Peter Wang (王信友) <peter.wang@...iatek.com>
To: "powenkao@...gle.com" <powenkao@...gle.com>
CC: "beanhuo@...ron.com" <beanhuo@...ron.com>, "avri.altman@....com"
	<avri.altman@....com>, "quic_nguyenb@...cinc.com" <quic_nguyenb@...cinc.com>,
	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	"bvanassche@....org" <bvanassche@....org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "alim.akhtar@...sung.com"
	<alim.akhtar@...sung.com>, "adrian.hunter@...el.com"
	<adrian.hunter@...el.com>, "mani@...nel.org" <mani@...nel.org>,
	"James.Bottomley@...senPartnership.com"
	<James.Bottomley@...senPartnership.com>, "martin.petersen@...cle.com"
	<martin.petersen@...cle.com>
Subject: Re: [PATCH 1/1] scsi: ufs: core: Fix EH failure after wlun resume
 error

On Wed, 2025-11-12 at 06:32 +0000, Po-Wen Kao wrote:
>   google-ufshcd 3c2d0000.ufs: ufshcd_err_handler started; HBA state
> eh_fatal; ...
>   ufs_device_wlun 0:0:0:49488: START_STOP failed for power mode: 1,
> result 40000
>   ufs_device_wlun 0:0:0:49488: ufshcd_wl_runtime_resume failed: -5
>   ...
>   ufs_device_wlun 0:0:0:49488: runtime PM trying to activate child
> device 0:0:0:49488 but parent (target0:0:0) is not active
> 

Hi Brian,

How is ufshcd_err_handler triggered before the parent device
resumes? I mean, what causes ufshcd_err_handler to be 
triggered, an error interrupt or something else?

Thanks
Peter