linux-kernel - Re: [PATCH] firmware: smccc: default ARM_SMCCC_SOC

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 for Android: free password hash cracker in your pocket

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

Message-ID: <t4pd72ff2ut4xr7ke3tzn3vxhyxq4kr6m3tublurwchynonouj@y4jgc3zqa5tw>
Date: Thu, 15 Jan 2026 18:01:57 -0600
From: Bjorn Andersson <andersson@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Satya Durga Srinivasu Prabhala <satya.prabhala@....qualcomm.com>, 
	Sudeep Holla <sudeep.holla@....com>, Mark Rutland <mark.rutland@....com>, 
	Lorenzo Pieralisi <lpieralisi@...nel.org>, linux-arm-msm@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, trilok.soni@....qualcomm.com
Subject: Re: [PATCH] firmware: smccc: default ARM_SMCCC_SOC_ID to disabled

On Thu, Jan 15, 2026 at 10:18:38PM +0200, Dmitry Baryshkov wrote:
> On Thu, Jan 15, 2026 at 10:42:51AM -0800, Satya Durga Srinivasu Prabhala wrote:
[..]
> 
> The kernel was never broken, it is not a kernel change that introduced
> the regression. Why are you trying to change the kernel?

I always thought you had one of these per SoC, so assuming a that a
single-soc system presented one entry would make sense to me.

The kernel is supposed to abstract away hardware details, that's clearly
not what we're doing here.

> If it ain't broken, don't fix it.
> 

Get over yourself.

Regards,
Bjorn