linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Richter <tmricht@linux.ibm.com>
To: James Clark <james.clark@linaro.org>
Cc: agordeev@linux.ibm.com, gor@linux.ibm.com,
	sumanthk@linux.ibm.com, hca@linux.ibm.com,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-perf-users@vger.kernel.org, acme@kernel.org,
	namhyung@kernel.org, irogers@google.com
Subject: Re: [PATCH] perf pmu: Handle memory failure in tool_pmu__new()
Date: Wed, 19 Mar 2025 13:28:02 +0100	[thread overview]
Message-ID: <552882a0-936d-439b-a5ed-b852bd39f9d6@linux.ibm.com> (raw)
In-Reply-To: <9f9c007a-78fe-4709-9063-eb4df72d4f63@linaro.org>

On 3/19/25 10:58, James Clark wrote:
> 
> 
> On 19/03/2025 9:28 am, Thomas Richter wrote:
>> On linux-next
>> commit 72c6f57a4193 ("perf pmu: Dynamically allocate tool PMU")
>> allocated PMU named "tool" dynamicly. However that allocation
>> can fail and a NULL pointer is returned. That case is currently
>> not handled and would result in an invalid address reference.
>> Add a check for NULL pointer.
>>
>> Fixes: 72c6f57a4193 ("perf pmu: Dynamically allocate tool PMU")
>> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
>> Cc: Ian Rogers <irogers@google.com>
>> Cc: James Clark <james.clark@linaro.org>
>> ---
>>   tools/perf/util/pmus.c     | 3 ++-
>>   tools/perf/util/tool_pmu.c | 9 +++++++++
>>   2 files changed, 11 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/util/pmus.c b/tools/perf/util/pmus.c
>> index 9b5a63ecb249..b99292de7669 100644
>> --- a/tools/perf/util/pmus.c
>> +++ b/tools/perf/util/pmus.c
>> @@ -265,7 +265,8 @@ static void pmu_read_sysfs(unsigned int to_read_types)
>>       if ((to_read_types & PERF_TOOL_PMU_TYPE_TOOL_MASK) != 0 &&
>>           (read_pmu_types & PERF_TOOL_PMU_TYPE_TOOL_MASK) == 0) {
>>           tool_pmu = tool_pmu__new();
>> -        list_add_tail(&tool_pmu->list, &other_pmus);
>> +        if (tool_pmu)
>> +            list_add_tail(&tool_pmu->list, &other_pmus);
>>       }
>>       if ((to_read_types & PERF_TOOL_PMU_TYPE_HWMON_MASK) != 0 &&
>>           (read_pmu_types & PERF_TOOL_PMU_TYPE_HWMON_MASK) == 0)
>> diff --git a/tools/perf/util/tool_pmu.c b/tools/perf/util/tool_pmu.c
>> index b60ac390d52d..d764c4734be6 100644
>> --- a/tools/perf/util/tool_pmu.c
>> +++ b/tools/perf/util/tool_pmu.c
>> @@ -495,12 +495,21 @@ struct perf_pmu *tool_pmu__new(void)
>>   {
>>       struct perf_pmu *tool = zalloc(sizeof(struct perf_pmu));
>>   +    if (!tool)
>> +        goto out;
>>       tool->name = strdup("tool");
>> +    if (!tool->name) {
>> +        zfree(tool);
>> +        tool = NULL;
> 
> Hi Thomas,
> 
> zfree() already sets the thing to NULL but you need to pass a pointer to it:
> 
>   zfree(&tool);
> 
> Without doing that you only free the first u64 of the struct, which happens to be zero in this case so free() does nothing. Then zfree() sets the first u64 of the struct to zero which it already is.
> 
> With that fixed:
> 
> Reviewed-by: James Clark <james.clark@linaro.org>
> 
> 

Thanks for the finding. I'll post verion 2 soon.

-- 
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
IBM Deutschland Research & Development GmbH

Vorsitzender des Aufsichtsrats: Wolfgang Wendt

Geschäftsführung: David Faller

Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294

      reply	other threads:[~2025-03-19 12:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19  9:28 [PATCH] perf pmu: Handle memory failure in tool_pmu__new() Thomas Richter
2025-03-19  9:58 ` James Clark
2025-03-19 12:28   ` Thomas Richter [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=552882a0-936d-439b-a5ed-b852bd39f9d6@linux.ibm.com \
    --to=tmricht@linux.ibm.com \
    --cc=acme@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=sumanthk@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).