From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, ionela.voinescu@arm.com,
sudeep.holla@arm.com, catalin.marinas@arm.com,
Beata Michalska <beata.michalska@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
sumitg@nvidia.com, ptsm@linux.microsoft.com
Subject: Re: [PATCH] arm64: amu: Delay allocating cpumask for AMU FIE support
Date: Thu, 13 Feb 2025 13:59:01 +0000 [thread overview]
Message-ID: <173944478263.2605897.5555784632946781698.b4-ty@kernel.org> (raw)
In-Reply-To: <20250131155842.3839098-1-beata.michalska@arm.com>
On Fri, 31 Jan 2025 15:58:42 +0000, Beata Michalska wrote:
> For the time being, the amu_fie_cpus cpumask is being exclusively used
> by the AMU-related internals of FIE support and is guaranteed to be
> valid on every access currently made. Still the mask is not being
> invalidated on one of the error handling code paths, which leaves
> a soft spot with theoretical risk of UAF for CPUMASK_OFFSTACK cases.
> To make things sound, delay allocating said cpumask
> (for CPUMASK_OFFSTACK) avoiding otherwise nasty sanitising case failing
> to register the cpufreq policy notifications.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: amu: Delay allocating cpumask for AMU FIE support
https://git.kernel.org/arm64/c/d923782b0412
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-02-13 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 15:58 Beata Michalska
2025-01-31 16:34 ` Sudeep Holla
2025-02-13 13:59 ` 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=173944478263.2605897.5555784632946781698.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ptsm@linux.microsoft.com \
--cc=sudeep.holla@arm.com \
--cc=sumitg@nvidia.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
all inboxes | Powered by JetHome®