From: Shuah Khan <skhan@linuxfoundation.org>
To: longlong yan <yanlonglong@kylinos.cn>, trenn@suse.com
Cc: shuah@kernel.org, jwyatt@redhat.com, sageofredondo@gmail.com,
jkacur@redhat.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] cpupower: idle_monitor: add NULL check after calloc()
Date: Fri, 4 Sep 2026 12:00:24 -0600 [thread overview]
Message-ID: <269fd99d-b031-430e-a917-78ae97d9bd0e@linuxfoundation.org> (raw)
In-Reply-To: <20260902065224.1392-1-yanlonglong@kylinos.cn>
On 9/2/26 00:52, longlong yan wrote:
> Twenty calloc() calls across five idle monitor files lack NULL return
> checks, leading to potential NULL pointer dereferences on allocation
> failure:
>
> - mperf_monitor.c mperf_register(): nine consecutive calloc() calls
> for per-CPU counters are used directly without any NULL check.
> - snb_idle.c snb_register(): is_valid and per-CSTATE previous/current
> counters are allocated without NULL checks.
> - nhm_idle.c intel_nhm_register(): same pattern as snb_idle.
> - hsw_ext_idle.c hsw_ext_register(): same pattern as snb_idle.
> - amd_fam14h_idle.c amd_fam14h_register(): per-state previous/current
> counters are allocated without NULL checks.
>
> Add NULL checks after each allocation, returning NULL on failure,
> consistent with existing error handling in the same functions (e.g.,
> hardware capability checks already return NULL on failure).
There is no need to add null checks for these small amounts
of memory from tools like this one.
How did you test these error paths?
Sorry I won't take this patch.
>
> Signed-off-by: longlong yan <yanlonglong@kylinos.cn>
> ---
> tools/power/cpupower/utils/idle_monitor/amd_fam14h_idle.c | 2 ++
> tools/power/cpupower/utils/idle_monitor/hsw_ext_idle.c | 4 ++++
> tools/power/cpupower/utils/idle_monitor/mperf_monitor.c | 5 +++++
> tools/power/cpupower/utils/idle_monitor/nhm_idle.c | 4 ++++
> tools/power/cpupower/utils/idle_monitor/snb_idle.c | 4 ++++
> 5 files changed, 19 insertions(+)
>
thanks,
-- Shuah
prev parent reply other threads:[~2026-09-04 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 6:52 [PATCH] cpupower: idle_monitor: add NULL check after calloc() longlong yan
2026-09-04 18:00 ` Shuah Khan [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=269fd99d-b031-430e-a917-78ae97d9bd0e@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sageofredondo@gmail.com \
--cc=shuah@kernel.org \
--cc=trenn@suse.com \
--cc=yanlonglong@kylinos.cn \
/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