linux-kernel - Re: [PATCH v4] scsi: ufs: core: Don't perform UFS clkscale if host asyn scan in progress

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: <ea382e7c-2436-4e82-a2b5-d5b7737b8828@acm.org>
Date: Wed, 30 Jul 2025 08:37:16 -0700
From: Bart Van Assche <bvanassche@....org>
To: Peter Wang (王信友) <peter.wang@...iatek.com>,
 "beanhuo@...ron.com" <beanhuo@...ron.com>,
 "avri.altman@....com" <avri.altman@....com>,
 "neil.armstrong@...aro.org" <neil.armstrong@...aro.org>,
 "quic_cang@...cinc.com" <quic_cang@...cinc.com>,
 "quic_nitirawa@...cinc.com" <quic_nitirawa@...cinc.com>,
 "quic_nguyenb@...cinc.com" <quic_nguyenb@...cinc.com>,
 "quic_ziqichen@...cinc.com" <quic_ziqichen@...cinc.com>,
 "luca.weiss@...rphone.com" <luca.weiss@...rphone.com>,
 "konrad.dybcio@....qualcomm.com" <konrad.dybcio@....qualcomm.com>,
 "mani@...nel.org" <mani@...nel.org>,
 "martin.petersen@...cle.com" <martin.petersen@...cle.com>,
 "quic_rampraka@...cinc.com" <quic_rampraka@...cinc.com>,
 "junwoo80.lee@...sung.com" <junwoo80.lee@...sung.com>
Cc: "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
 Tze-nan Wu (吳澤南) <Tze-nan.Wu@...iatek.com>,
 "linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
 "manivannan.sadhasivam@...aro.org" <manivannan.sadhasivam@...aro.org>,
 "alim.akhtar@...sung.com" <alim.akhtar@...sung.com>,
 "James.Bottomley@...senPartnership.com"
 <James.Bottomley@...senPartnership.com>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4] scsi: ufs: core: Don't perform UFS clkscale if host
 asyn scan in progress

On 7/30/25 5:55 AM, Peter Wang (王信友) wrote:
> However, in theory, this issue should still be solvable
> without using a lock.
> Another idea is to only start ufshcd_devfreq_init
> when shost->async_scan = 0.

Does the lockdep complaint mentioned in this email thread occur on
multiple platforms or only on MediaTek platforms? I don't see any
lockdep complaints with Martin's SCSI for-next branch on my
development platform. If this warning only occurs on MediaTek
platforms, why to modify the UFSHCI core driver to eliminate this
lockdep complaint?

Thanks,

Bart.