From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf pmu: Avoid segv for missing name/alias_name in wildcarding
Date: Tue, 27 May 2025 17:57:17 -0300 [thread overview]
Message-ID: <aDYnLedM8RT17FHx@x1> (raw)
In-Reply-To: <CAP-5=fUiWm9kq2fhT-9+8LOmC2Yen9Mw2P8yPLTJH+nk83nmmA@mail.gmail.com>
On Tue, May 27, 2025 at 01:33:35PM -0700, Ian Rogers wrote:
> On Fri, Apr 4, 2025 at 11:07 AM Namhyung Kim <namhyung@kernel.org> wrote:
> > On Wed, Apr 02, 2025 at 02:13:01PM -0700, Ian Rogers wrote:
> > > The pmu name or alias_name fields may be NULL and should be skipped if
> > > so. This is done in all loops of perf_pmu___name_match except the
> > > final wildcard loop which was an oversight.
> > > Fixes: c786468a3585 ("perf pmu: Rename name matching for no suffix or wildcard variants")
> > > Signed-off-by: Ian Rogers <irogers@google.com>
> > Acked-by: Namhyung Kim <namhyung@kernel.org>
> Ping.
⬢ [acme@toolbx perf-tools-next]$ patch -p1 < ./20250402_irogers_perf_pmu_avoid_segv_for_missing_name_alias_name_in_wildcarding.mbx
patching file tools/perf/util/pmu.c
Hunk #1 FAILED at 2060.
1 out of 1 hunk FAILED -- saving rejects to file tools/perf/util/pmu.c.rej
⬢ [acme@toolbx perf-tools-next]$
⬢ [acme@toolbx perf-tools-next]$ cat tools/perf/util/pmu.c.rej
--- tools/perf/util/pmu.c
+++ tools/perf/util/pmu.c
@@ -2060,7 +2060,9 @@ static bool perf_pmu___name_match(const struct perf_pmu *pmu, const char *to_mat
}
for (size_t i = 0; i < ARRAY_SIZE(names); i++) {
const char *name = names[i];
-
+
+ if (!name)
+ continue;
if (wildcard && perf_pmu__match_wildcard_uncore(name, to_match))
return true;
if (!wildcard && perf_pmu__match_ignoring_suffix_uncore(name, to_match))
⬢ [acme@toolbx perf-tools-next]$
⬢ [acme@toolbx perf-tools-next]$ git log --oneline -5 tools/perf/util/pmu.c
754baf426e099fbf perf pmu: Change aliases from list to hashmap
255f5b6d060be5a4 perf parse-events: Add "cpu" term to set the CPU an event is recorded on
fa1332a8011eebe1 perf mem/c2c amd: Add ldlat support
fc807b6bde6ad332 perf pmu-events: Add retirement latency to JSON events inside of perf
58b8b5d142a8bd5c perf cpumap: Increment reference count for online cpumap
⬢ [acme@toolbx perf-tools-next]$
Can you please take a look?
- Arnaldo
next prev parent reply other threads:[~2025-05-27 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 21:13 [PATCH v1] perf pmu: Avoid segv for missing name/alias_name in wildcarding Ian Rogers
2025-04-04 18:07 ` Namhyung Kim
2025-05-27 20:33 ` Ian Rogers
2025-05-27 20:57 ` Arnaldo Carvalho de Melo [this message]
2025-05-27 21:52 ` Ian Rogers
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=aDYnLedM8RT17FHx@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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