From: Sumit Gupta <sumitg@nvidia.com>
To: Beata Michalska <beata.michalska@arm.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-pm@vger.kernel.org>, <ionela.voinescu@arm.com>,
<sudeep.holla@arm.com>, <will@kernel.org>,
<catalin.marinas@arm.com>, <rafael@kernel.org>,
<viresh.kumar@linaro.org>
Cc: <yang@os.amperecomputing.com>,
<vanshikonda@os.amperecomputing.com>, <lihuisong@huawei.com>,
<zhanjie9@hisilicon.com>,
linux-tegra <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v9 3/5] arm64: amu: Delay allocating cpumask for AMU FIE support
Date: Wed, 29 Jan 2025 16:47:36 +0530 [thread overview]
Message-ID: <1465513a-1752-48f3-80f1-321d1e7f357a@nvidia.com> (raw)
In-Reply-To: <20250121084435.2839280-4-beata.michalska@arm.com>
On 21/01/25 14:14, 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.
>
> Signed-off-by: Beata Michalska <beata.michalska@arm.com>
Reviewed-by: Sumit Gupta <sumitg@nvidia.com>
> ---
> arch/arm64/kernel/topology.c | 22 ++++++++++------------
> 1 file changed, 10 insertions(+), 12 deletions(-)
>
> diff --git a/arch/arm64/kernel/topology.c b/arch/arm64/kernel/topology.c
> index 1a2c72f3e7f8..cb180684d10d 100644
> --- a/arch/arm64/kernel/topology.c
> +++ b/arch/arm64/kernel/topology.c
> @@ -194,12 +194,19 @@ static void amu_fie_setup(const struct cpumask *cpus)
> int cpu;
>
> /* We are already set since the last insmod of cpufreq driver */
> - if (unlikely(cpumask_subset(cpus, amu_fie_cpus)))
> + if (cpumask_available(amu_fie_cpus) &&
> + unlikely(cpumask_subset(cpus, amu_fie_cpus)))
> return;
>
> - for_each_cpu(cpu, cpus) {
> + for_each_cpu(cpu, cpus)
> if (!freq_counters_valid(cpu))
> return;
> +
> + if (!cpumask_available(amu_fie_cpus) &&
> + !zalloc_cpumask_var(&amu_fie_cpus, GFP_KERNEL)) {
> + WARN_ONCE(1, "Failed to allocate FIE cpumask for CPUs[%*pbl]\n",
> + cpumask_pr_args(cpus));
> + return;
> }
>
> cpumask_or(amu_fie_cpus, amu_fie_cpus, cpus);
> @@ -237,17 +244,8 @@ static struct notifier_block init_amu_fie_notifier = {
>
> static int __init init_amu_fie(void)
> {
> - int ret;
> -
> - if (!zalloc_cpumask_var(&amu_fie_cpus, GFP_KERNEL))
> - return -ENOMEM;
> -
> - ret = cpufreq_register_notifier(&init_amu_fie_notifier,
> + return cpufreq_register_notifier(&init_amu_fie_notifier,
> CPUFREQ_POLICY_NOTIFIER);
> - if (ret)
> - free_cpumask_var(amu_fie_cpus);
> -
> - return ret;
> }
> core_initcall(init_amu_fie);
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2025-01-29 11:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 8:44 [PATCH v9 0/5] Add support for AArch64 AMUv1-based average freq Beata Michalska
2025-01-21 8:44 ` [PATCH v9 1/5] cpufreq: Allow arch_freq_get_on_cpu to return an error Beata Michalska
2025-01-21 10:47 ` Viresh Kumar
2025-01-21 15:14 ` Beata Michalska
2025-01-21 18:40 ` Vanshidhar Konda
2025-01-23 21:37 ` Beata Michalska
2025-01-22 6:12 ` Viresh Kumar
2025-01-23 21:45 ` Beata Michalska
2025-01-24 3:33 ` Viresh Kumar
2025-01-28 8:09 ` Beata Michalska
2025-01-28 8:18 ` Viresh Kumar
2025-01-21 10:47 ` Prasanna Kumar T S M
2025-01-24 4:15 ` Prasanna Kumar T S M
2025-01-21 8:44 ` [PATCH v9 2/5] cpufreq: Introduce an optional cpuinfo_avg_freq sysfs entry Beata Michalska
2025-01-21 10:53 ` Viresh Kumar
2025-01-21 15:17 ` Beata Michalska
2025-01-22 6:09 ` Viresh Kumar
2025-01-23 21:47 ` Beata Michalska
2025-01-24 3:27 ` Viresh Kumar
2025-01-28 8:43 ` Prasanna Kumar T S M
2025-01-29 11:29 ` Sumit Gupta
2025-01-21 8:44 ` [PATCH v9 3/5] arm64: amu: Delay allocating cpumask for AMU FIE support Beata Michalska
2025-01-24 4:48 ` Prasanna Kumar T S M
2025-01-29 11:17 ` Sumit Gupta [this message]
2025-01-21 8:44 ` [PATCH v9 4/5] arm64: Provide an AMU-based version of arch_freq_get_on_cpu Beata Michalska
2025-01-24 4:43 ` Prasanna Kumar T S M
2025-01-28 8:16 ` Beata Michalska
2025-01-28 8:52 ` Prasanna Kumar T S M
2025-01-29 11:15 ` Sumit Gupta
2025-01-21 8:44 ` [PATCH v9 5/5] arm64: Update AMU-based freq scale factor on entering idle Beata Michalska
2025-01-24 4:45 ` Prasanna Kumar T S M
2025-01-29 11:13 ` Sumit Gupta
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=1465513a-1752-48f3-80f1-321d1e7f357a@nvidia.com \
--to=sumitg@nvidia.com \
--cc=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=lihuisong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vanshikonda@os.amperecomputing.com \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.com \
--cc=zhanjie9@hisilicon.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®