From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>, Hui Su <sh_def@163.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf evsel: Restrict incremental open error unwind
Date: Tue, 22 Sep 2026 14:35:12 +0200 [thread overview]
Message-ID: <arJ2AHXSkPcwnq7e@x2> (raw)
In-Reply-To: <CAP-5=fUWC6F+_HCqW7eFuaw5StZpdcpb+pXPdHbXE+auNdMdTw@mail.gmail.com>
On Mon, Sep 21, 2026 at 09:00:43AM -0700, Ian Rogers wrote:
> On Sun, Sep 13, 2026 at 6:17 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > On Sat, Sep 12, 2026 at 12:11:10PM +0900, Hui Su wrote:
> > > evsel__open_cpu(), evsel__tool_pmu_open() and
> > > evsel__hwmon_pmu_open() support opening a subrange of a CPU map, bounded
> > > by [start_cpu_map_idx, end_cpu_map_idx).
> > >
> > > Their error paths, however, unwind using "while (--idx >= 0)" all the way
> > > back to CPU index 0 regardless of start_cpu_map_idx. If lower CPU indices
> > > were opened by an earlier invocation, a later incremental open failure
> > > therefore closes those existing file descriptors and overwrites their
> > > slots with -1.
> > >
> > > Before this fix, running the new incremental open test demonstrates this
> > > corruption:
> > >
> > > $ perf test -v "Tool PMU"
> > > 12: Tool PMU:
> > > 12.1: Tool PMU : Ok
> > > 12.2: Tool PMU leader : Ok
> > > 12.3: Incremental open error unwind boundary:
> > > FAILED: CPU 0 FD overwritten: FD(evsel, 0, 0)=-1, expected 4
> > > FAILED!
> > >
> > > Stop the unwind at start_cpu_map_idx so that only file descriptors
> > > opened by the current invocation are rolled back.
> > >
> > > After this fix:
> > >
> > > $ perf test -v "Tool PMU"
> > > 12: Tool PMU:
> > > 12.1: Tool PMU : Ok
> > > 12.2: Tool PMU leader : Ok
> > > 12.3: Incremental open error unwind boundary : Ok
> > >
> > > Fixes: 4804e0111662 ("perf stat: Use affinity for opening events")
> > > Fixes: 240505b2d0ad ("perf tool_pmu: Factor tool events into their own PMU")
> > > Fixes: 53cc0b351ec9 ("perf hwmon_pmu: Add a tool PMU exposing events from hwmon in sysfs")
> >
> > Maybe we just need to last one?
> >
> > Acked-by: Namhyung Kim <namhyung@kernel.org>
>
> Reviewed-by: Ian Rogers <irogers@google.com>
Thanks, applied to perf-tools-next, for v7.4.
- Arnaldo
prev parent reply other threads:[~2026-09-22 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 3:11 Hui Su
2026-09-14 1:17 ` Namhyung Kim
2026-09-21 16:00 ` Ian Rogers
2026-09-22 12:35 ` Arnaldo Carvalho de Melo [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=arJ2AHXSkPcwnq7e@x2 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sh_def@163.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
all inboxes | Powered by JetHome®