From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
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>,
Chun-Tse Shao <ctshao@google.com>,
James Clark <james.clark@linaro.org>,
Howard Chu <howardchu95@gmail.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1 2/4] perf test: Don't leak workload gopipe in PERF_RECORD_*
Date: Tue, 16 Sep 2025 22:06:25 -0300 [thread overview]
Message-ID: <aMoJkR_jtzrGCLKI@x1> (raw)
In-Reply-To: <CAP-5=fU8NXY+mbnkmhq15yncXx0TxE7Zc1zu23o+d+3ZyXjSjA@mail.gmail.com>
On Tue, Sep 16, 2025 at 12:08:58PM -0700, Ian Rogers wrote:
> On Tue, Sep 16, 2025 at 12:04 PM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > On Thu, Aug 21, 2025 at 03:18:32PM -0700, Ian Rogers wrote:
> > > The test starts a workload and then opens events. If the events fail
> > > to open, for example because of perf_event_paranoid, the gopipe of the
> > > workload is leaked and the file descriptor leak check fails when the
> > > test exits. To avoid this cancel the workload when opening the events
> > > fails.
> > > Before:
> > > ```
> > > $ perf test -vv 7
> > > 7: PERF_RECORD_* events & perf_sample fields:
> > > --- start ---
> > ⬢ [acme@toolbx perf-tools-next]$ patch -p1 < b
> > patching file tools/perf/tests/perf-record.c
> > Hunk #1 succeeded at 130 (offset 15 lines).
> > Hunk #2 succeeded at 142 with fuzz 1 (offset 15 lines).
> > Hunk #3 succeeded at 154 (offset 15 lines).
> > Hunk #4 succeeded at 167 (offset 15 lines).
> > ⬢ [acme@toolbx perf-tools-next]$
> > ⬢ [acme@toolbx perf-tools-next]$ git log --oneline -5 tools/perf/tests/perf-record.c
> > 576bd7a8c90c48e9 (x1/perf-tools-next, x1/HEAD, five/perf-tools-next, five/HEAD) perf tests record: Update testcase to fix usage of affinity for machines with #CPUs > 1K
> > b4c658d4d63d6149 perf target: Remove uid from target
> > dc6d2bc2d893a878 perf sample: Make user_regs and intr_regs optional
> > fd8d5a3b076c033f perf tests: Add missing event.h include
> > 9823147da6c893d9 perf tools: Move 'struct perf_sample' to a separate header file to disentangle headers
> > ⬢ [acme@toolbx perf-tools-next]$
> > Can you please check that it is still ok?
> > I processed the first in the series and now I'm going thru the other
> > two.
> Thanks Arnaldo! I'm not seeing the patch on:
> https://web.git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/log/?h=tmp.perf-tools-next
Sorry, I thought I had pushed it earlier, should be there now.
> I'm happy to check.
Thanks!
- Arnaldo
next prev parent reply other threads:[~2025-09-17 1:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 22:18 [PATCH v1 0/4] Test/uniquification related fixes Ian Rogers
2025-08-21 22:18 ` [PATCH v1 1/4] perf test shell lbr: Avoid failures with perf event paranoia Ian Rogers
2025-09-16 19:00 ` Arnaldo Carvalho de Melo
2025-08-21 22:18 ` [PATCH v1 2/4] perf test: Don't leak workload gopipe in PERF_RECORD_* Ian Rogers
2025-09-16 19:04 ` Arnaldo Carvalho de Melo
2025-09-16 19:08 ` Ian Rogers
2025-09-17 1:06 ` Arnaldo Carvalho de Melo [this message]
2025-09-18 22:17 ` Ian Rogers
2025-08-21 22:18 ` [PATCH v1 3/4] perf evsel: Fix uniquification when PMU given without suffix Ian Rogers
2025-08-21 22:18 ` [PATCH v1 4/4] perf test: Avoid uncore_imc/clockticks in uniquification test Ian Rogers
2025-09-16 19:15 ` Arnaldo Carvalho de Melo
2025-09-16 20:45 ` 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=aMoJkR_jtzrGCLKI@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ctshao@google.com \
--cc=howardchu95@gmail.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;
as well as URLs for NNTP newsgroup(s).