From: sashiko-bot@kernel.org
To: "Namhyung Kim" <namhyung@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf stat: Do not open cgroups for BPF counters
Date: Wed, 08 Jul 2026 20:14:33 +0000 [thread overview]
Message-ID: <20260708201434.5C5831F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260708200407.1240640-1-namhyung@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Fallback from BPF counter mode to standard cgroup mode leaves cgroup file descriptors uninitialized (-1), causing standard perf event opening to fail with -EBADF.
--
--- Patch [1]: [PATCH] perf stat: Do not open cgroups for BPF counters ---
commit 510c63ce03b2362940d1f693b45d5faa86cf3bc1
Author: Namhyung Kim <namhyung@kernel.org>
perf stat: Do not open cgroups for BPF counters
This commit prevents opening and keeping file descriptors for cgroups
when using the --bpf-counters and --for-each-cgroup options. BPF mode
uses a set of shared events and compares cgroup-IDs, so it doesn't need
individual cgroup file descriptors.
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -2874,7 +2874,8 @@ int cmd_stat(int argc, const char **argv)
> goto out;
> }
>
> - if (evlist__expand_cgroup(evsel_list, stat_config.cgroup_list, true) < 0) {
> + if (evlist__expand_cgroup(evsel_list, stat_config.cgroup_list,
> + !target.use_bpf) < 0) {
[Severity: Medium]
Will this break the fallback path when we exceed BPERF_CGROUP__MAX_EVENTS?
Later in cmd_stat(), we have a fallback that disables BPF counters if there
are too many events:
if (target.use_bpf && nr_cgroups &&
(evsel_list->core.nr_entries / nr_cgroups) > BPERF_CGROUP__MAX_EVENTS) {
pr_warning("Disabling BPF counters due to more events...");
target.use_bpf = false;
}
If this fallback is triggered, target.use_bpf becomes false, but the cgroups
were already expanded with !target.use_bpf (which was false at the time),
leaving the cgroup file descriptors uninitialized (-1).
When the standard event opening later calls evsel__open_cpu() in
tools/perf/util/evsel.c:
if (evsel->cgrp)
pid = evsel->cgrp->fd;
Could it attempt to use the uninitialized cgroup file descriptor (-1) with
the perf_event_open syscall, causing it to fail with -EBADF? Should the
cgroup file descriptors be reopened if the fallback to standard mode is
taken?
> parse_options_usage(stat_usage, stat_options,
> "for-each-cgroup", 0);
> goto out;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260708200407.1240640-1-namhyung@kernel.org?part=1
next prev parent reply other threads:[~2026-07-08 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 20:04 [PATCH] perf stat: Do not open cgroups for BPF counters Namhyung Kim
2026-07-08 20:14 ` sashiko-bot [this message]
2026-07-10 23:50 ` Namhyung Kim
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=20260708201434.5C5831F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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