From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>, Mark Brown <broonie@kernel.org>,
Will Deacon <will@kernel.org>, Dave Martin <Dave.Martin@arm.com>
Subject: Re: [PATCH V4] arm64/cpuinfo: Define HWCAP name arrays per their actual bit definitions
Date: Fri, 11 Sep 2020 16:31:49 +0100 [thread overview]
Message-ID: <159983818680.1465915.16143462979896283824.b4-ty@kernel.org> (raw)
In-Reply-To: <1599630535-29337-1-git-send-email-anshuman.khandual@arm.com>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-09-11 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 5:48 [PATCH V4] arm64/cpuinfo: Define HWCAP name arrays per their actual bit definitions Anshuman Khandual
2020-09-11 15:24 ` Catalin Marinas
2020-09-11 15:31 ` Will Deacon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=159983818680.1465915.16143462979896283824.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).