From: sivany32@gmail.com
To: linux-pm@vger.kernel.org
Cc: rafael@kernel.org, daniel.lezcano@kernel.org,
linux-kernel@vger.kernel.org, elazarl@gmail.com,
Sivan Zohar-Kotzer <sivany32@gmail.com>
Subject: [PATCH v2 1/2] powercap: dtpm_cpu: Guard em_cpu_get() against NULL return in sysfs callbacks
Date: Wed, 24 Jun 2026 23:31:47 +0300 [thread overview]
Message-ID: <20260624203147.67528-1-sivany32@gmail.com> (raw)
In-Reply-To: <20260611204658.47987-1-elazarl@gmail.com>
From: Sivan Zohar-Kotzer <sivany32@gmail.com>
em_cpu_get() can return NULL when a CPU becomes impossible. Two call
sites miss the NULL test:
1. set_pd_power_limit() — reachable from sysfs via the powercap
constraint power_limit_uw store path. If the CPU has become
impossible then pd will be NULL, return the current power limit
unchanged (no-op) instead of crashing.
2. update_pd_power_uw() — called from CPU hotplug handlers via
dtpm_update_power(). While reaching this with a NULL em may be
technically impossible today, the check is kept for defense in
depth against future refactoring or subtle races.
The other sysfs-reachable path, get_pd_power_uw(), already has a NULL
guard returning 0.
Fixes: 0e8f68d7f048 ("powercap/drivers/dtpm: Add CPU energy model based support")
Signed-off-by: Sivan Zohar-Kotzer <sivany32@gmail.com>
Co-developed-by: Elazar Leibovich <elazarl@gmail.com>
Signed-off-by: Elazar Leibovich <elazarl@gmail.com>
---
drivers/powercap/dtpm_cpu.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/powercap/dtpm_cpu.c b/drivers/powercap/dtpm_cpu.c
index 21355db64..886cbe922 100644
--- a/drivers/powercap/dtpm_cpu.c
+++ b/drivers/powercap/dtpm_cpu.c
@@ -47,6 +47,9 @@ static u64 set_pd_power_limit(struct dtpm *dtpm, u64 power_limit)
u64 power;
int i, nr_cpus;
+ if (!pd)
+ return dtpm->power_limit;
+
nr_cpus = cpumask_weight_and(cpu_online_mask, to_cpumask(pd->cpus));
rcu_read_lock();
@@ -125,6 +128,9 @@ static int update_pd_power_uw(struct dtpm *dtpm)
struct em_perf_state *table;
int nr_cpus;
+ if (!em)
+ return -EINVAL;
+
nr_cpus = cpumask_weight_and(cpu_online_mask, to_cpumask(em->cpus));
rcu_read_lock();
--
2.39.5 (Apple Git-154)
next prev parent reply other threads:[~2026-06-24 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 20:46 [PATCH 0/2] powercap: dtpm: Guard against missing energy model in dtpm callbacks Elazar Leibovich
2026-06-11 20:46 ` [PATCH 1/2] powercap: dtpm_cpu: Guard em_cpu_get() against NULL return in sysfs callbacks Elazar Leibovich
2026-06-23 10:12 ` Daniel Lezcano
2026-06-11 20:46 ` [PATCH 2/2] powercap: dtpm_devfreq: Guard em_pd_get() against NULL return in callbacks Elazar Leibovich
2026-06-24 20:31 ` sivany32 [this message]
2026-06-24 20:44 ` [PATCH v2 1/2] powercap: dtpm_cpu: Guard em_cpu_get() against NULL return in sysfs callbacks Daniel Lezcano
2026-06-24 21:03 ` Elazar Leibovich
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=20260624203147.67528-1-sivany32@gmail.com \
--to=sivany32@gmail.com \
--cc=daniel.lezcano@kernel.org \
--cc=elazarl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
/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