From: TAKANO Mitsuhiro <takano32@gmail.com>
To: linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
TAKANO Mitsuhiro <takano32@gmail.com>
Subject: [PATCH] perf evsel: Skip group members without fds when walking a group
Date: Fri, 23 Oct 2026 08:56:29 +0000 [thread overview]
Message-ID: <20261023085629.1694941-1-takano32@gmail.com> (raw)
A group led by a userspace PMU event and containing kernel events is
opened with group_fd = -1 for the members, because the kernel cannot
group a userspace PMU with a kernel one. The members are therefore
enabled from userspace when the leader is enabled, but their fd array is
not set up in that case, so perf_evsel__enable_cpu() dereferences a NULL
pointer:
$ perf stat -a -e '{user_time,cycles}' -- sleep 0.05
Segmentation fault
$ perf stat -a -e '{system_time,cycles}' -- sleep 0.05
Segmentation fault
Only the leaders of such a group are opened with an fd in this path.
Skip the members that have no fd, the same way __evlist__enable() skips
leaders without one, in the four loops that walk the members of a group.
Verified on an Ampere Altra (arm64, Neoverse-N1) with a perf built from
this tree: the two commands above segfault before the change and print
user_time/system_time after it, while plain groups such as
'{cycles,instructions}', 'perf stat' with no event and '-r 2' are
unchanged.
Fixes: 0b18bced5444 ("perf tool_pmu: Make tool PMU events respect enable/disable")
Assisted-by: LLM
Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>
---
tools/perf/util/evsel.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
index d4cb455f4a7d..32c54cd4acf0 100644
--- a/tools/perf/util/evsel.c
+++ b/tools/perf/util/evsel.c
@@ -1882,6 +1882,8 @@ int evsel__enable_cpu(struct evsel *evsel, int cpu_map_idx)
struct evsel *member;
for_each_group_member(member, evsel) {
+ if (!member->core.fd)
+ continue;
if (evsel__is_non_perf_event_open_pmu(evsel) ||
evsel__is_non_perf_event_open_pmu(member)) {
/*
@@ -1917,6 +1919,8 @@ int evsel__enable(struct evsel *evsel)
struct evsel *member;
for_each_group_member(member, evsel) {
+ if (!member->core.fd)
+ continue;
if (evsel__is_non_perf_event_open_pmu(evsel) ||
evsel__is_non_perf_event_open_pmu(member)) {
/*
@@ -1952,6 +1956,8 @@ int evsel__disable_cpu(struct evsel *evsel, int cpu_map_idx)
struct evsel *member;
for_each_group_member(member, evsel) {
+ if (!member->core.fd)
+ continue;
if (evsel__is_non_perf_event_open_pmu(evsel) ||
evsel__is_non_perf_event_open_pmu(member)) {
/*
@@ -1992,6 +1998,8 @@ int evsel__disable(struct evsel *evsel)
struct evsel *member;
for_each_group_member(member, evsel) {
+ if (!member->core.fd)
+ continue;
if (evsel__is_non_perf_event_open_pmu(evsel) ||
evsel__is_non_perf_event_open_pmu(member)) {
/*
base-commit: f47d223627f80cb7a1eb14c585fe6cb35de5e984
--
2.53.0
next reply other threads:[~2026-10-23 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 8:56 TAKANO Mitsuhiro [this message]
2026-10-23 9:20 ` [PATCH] perf evsel: Skip group members without fds when walking a group sashiko-bot
2026-10-23 16:24 ` TAKANO Mitsuhiro
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=20261023085629.1694941-1-takano32@gmail.com \
--to=takano32@gmail.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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