[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <159983818680.1465915.16143462979896283824.b4-ty@kernel.org>
Date: Fri, 11 Sep 2020 16:31:49 +0100
From: Will Deacon <will@...nel.org>
To: linux-arm-kernel@...ts.infradead.org, catalin.marinas@....com,
Anshuman Khandual <anshuman.khandual@....com>
Cc: kernel-team@...roid.com, Will Deacon <will@...nel.org>,
Dave Martin <Dave.Martin@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Mark Brown <broonie@...nel.org>,
Mark Rutland <mark.rutland@....com>,
linux-kernel@...r.kernel.org, Ard Biesheuvel <ardb@...nel.org>
Subject: Re: [PATCH V4] arm64/cpuinfo: Define HWCAP name arrays per their actual bit definitions
On Wed, 9 Sep 2020 11:18:55 +0530, Anshuman Khandual wrote:
> HWCAP name arrays (hwcap_str, compat_hwcap_str, compat_hwcap2_str) that are
> scanned for /proc/cpuinfo are detached from their bit definitions making it
> vulnerable and difficult to correlate. It is also bit problematic because
> during /proc/cpuinfo dump these arrays get traversed sequentially assuming
> they reflect and match actual HWCAP bit sequence, to test various features
> for a given CPU. This redefines name arrays per their HWCAP bit definitions
> . It also warns after detecting any feature which is not expected on arm64.
Applied to arm64 (for-next/cpuinfo), thanks!
[1/1] arm64/cpuinfo: Define HWCAP name arrays per their actual bit definitions
https://git.kernel.org/arm64/c/4e56de82d4ec
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists