From: Chris Hyser <chris.hyser@oracle.com>
To: chris.hyser@oracle.com, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH] cpufreq: cppc_cpufreq: prevent crash on reading freqdomain_cpus
Date: Fri, 19 Aug 2022 15:03:57 -0400 [thread overview]
Message-ID: <1660935837-7481-2-git-send-email-chris.hyser@oracle.com> (raw)
In-Reply-To: <1660935837-7481-1-git-send-email-chris.hyser@oracle.com>
From: chris hyser <chris.hyser@oracle.com>
While running stress-ng --sysfs on an ARM system following a cpu offline,
we encountered the following NULL pointer dereference in the cppc_cpufreq
scaling driver:
[ 1003.576816] Call trace:
[ 1003.579255] _find_next_bit+0x20/0xc8
[ 1003.582909] cpufreq_show_cpus+0x78/0xf4
[ 1003.586830] show_freqdomain_cpus+0x20/0x30 [cppc_cpufreq]
[ 1003.592318] show+0x4c/0x78
[ 1003.595104] sysfs_kf_seq_show+0x9
This is the exact issue described in commit e25303676e18 ("cpufreq:
acpi_cpufreq: prevent crash on reading freqdomain_cpus") with the fix
described there also solving this issue. I tracked the root cause to the
following: a scaling driver which provides a struct freq_attr sysfs
attributes array passed via struct cpufreq_driver during driver
registration, has .init() and .exit() functions and does _not_ provide
.online()/.offline() routines. cpufreq core creates the attributes, but
does not remove them even though .exit() frees the underlying memory. The
core functions and most drivers have corresponding NULL data pointer
checks.
Signed-off-by: Chris Hyser <chris.hyser@oracle.com>
---
drivers/cpufreq/cppc_cpufreq.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/cpufreq/cppc_cpufreq.c b/drivers/cpufreq/cppc_cpufreq.c
index 24eaf0e..4210353 100644
--- a/drivers/cpufreq/cppc_cpufreq.c
+++ b/drivers/cpufreq/cppc_cpufreq.c
@@ -876,6 +876,9 @@ static ssize_t show_freqdomain_cpus(struct cpufreq_policy *policy, char *buf)
{
struct cppc_cpudata *cpu_data = policy->driver_data;
+ if (unlikely(!cpu_data))
+ return -ENODEV;
+
return cpufreq_show_cpus(cpu_data->shared_cpu_map, buf);
}
cpufreq_freq_attr_ro(freqdomain_cpus);
--
1.8.3.1
next prev parent reply other threads:[~2022-08-19 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 19:03 cpufreq: Scaling driver sysfs attribute issues Chris Hyser
2022-08-19 19:03 ` Chris Hyser [this message]
2022-08-22 5:39 ` [PATCH] cpufreq: cppc_cpufreq: prevent crash on reading freqdomain_cpus Viresh Kumar
2022-08-22 13:19 ` Chris Hyser
2022-08-22 15:54 ` Chris Hyser
2022-08-22 20:14 ` Chris Hyser
2022-08-23 4:13 ` Viresh Kumar
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=1660935837-7481-2-git-send-email-chris.hyser@oracle.com \
--to=chris.hyser@oracle.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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