linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Arnaldo Carvalho de Melo" <acme@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>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Jiapeng Chong" <jiapeng.chong@linux.alibaba.com>,
	"James Clark" <james.clark@linaro.org>,
	"Howard Chu" <howardchu95@gmail.com>,
	"Weilin Wang" <weilin.wang@intel.com>,
	"Stephen Brennan" <stephen.s.brennan@oracle.com>,
	"Andi Kleen" <ak@linux.intel.com>,
	"Dmitry Vyukov" <dvyukov@google.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] Various asan and test fixes
Date: Wed, 28 May 2025 11:02:36 -0700	[thread overview]
Message-ID: <aDdPvCIYmSPXmBJG@google.com> (raw)
In-Reply-To: <20250528032637.198960-1-irogers@google.com>

On Tue, May 27, 2025 at 08:26:30PM -0700, Ian Rogers wrote:
> When testing removing perf_env with asan I noticed a number of test
> failures either because of asan issues or because of building with
> NO_LIBELF=1 and NO_LIBBPF=1 to avoid false memory leaks. Address these
> issues so that real test failures stand out.
> 
> v2: Fix wrong elf size use in filename__read_build_id fix. Add
>     thread__comm_lock fix.
> 
> Ian Rogers (7):
>   perf symbol: Fix use-after-free in filename__read_build_id
>   perf test demangle-java: Don't segv if demangling fails
>   perf symbol: Move demangling code out of symbol-elf.c
>   perf intel-tpebs: Avoid race when evlist is being deleted
>   perf test intel-pt: Skip jitdump test if no libelf
>   perf test trace_summary: Skip --bpf-summary tests if no libbpf
>   perf thread: Avoid recursively taking thread__comm_lock

Acked-by: Namhyung Kim <namhyung@kernel.org>

Thanks,
Namhyung

> 
>  tools/perf/tests/demangle-java-test.c   |   5 +
>  tools/perf/tests/shell/test_intel_pt.sh |   5 +
>  tools/perf/tests/shell/trace_summary.sh |   6 +
>  tools/perf/util/demangle-cxx.h          |   2 +
>  tools/perf/util/intel-tpebs.c           |  12 +-
>  tools/perf/util/symbol-elf.c            |  86 ------------
>  tools/perf/util/symbol-minimal.c        | 175 ++++++++++--------------
>  tools/perf/util/symbol.c                |  87 ++++++++++++
>  tools/perf/util/thread.c                |  17 ++-
>  9 files changed, 198 insertions(+), 197 deletions(-)
> 
> -- 
> 2.49.0.1238.gf8c92423fb-goog
> 

      parent reply	other threads:[~2025-05-28 18:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28  3:26 [PATCH v2 0/7] Various asan and test fixes Ian Rogers
2025-05-28  3:26 ` [PATCH v2 1/7] perf symbol: Fix use-after-free in filename__read_build_id Ian Rogers
2025-05-28  3:26 ` [PATCH v2 2/7] perf test demangle-java: Don't segv if demangling fails Ian Rogers
2025-05-28  3:26 ` [PATCH v2 3/7] perf symbol: Move demangling code out of symbol-elf.c Ian Rogers
2025-05-28  3:26 ` [PATCH v2 4/7] perf intel-tpebs: Avoid race when evlist is being deleted Ian Rogers
2025-05-28 17:53   ` Namhyung Kim
2025-05-28 18:02     ` Ian Rogers
2025-05-28 20:13       ` Namhyung Kim
2025-05-28 20:44         ` Ian Rogers
2025-05-28 22:23           ` Namhyung Kim
2025-05-28  3:26 ` [PATCH v2 5/7] perf test intel-pt: Skip jitdump test if no libelf Ian Rogers
2025-05-28  3:26 ` [PATCH v2 6/7] perf test trace_summary: Skip --bpf-summary tests if no libbpf Ian Rogers
2025-05-28  4:17   ` Howard Chu
2025-05-28 12:56     ` Arnaldo Carvalho de Melo
2025-05-28  3:26 ` [PATCH v2 7/7] perf thread: Avoid recursively taking thread__comm_lock Ian Rogers
2025-05-28 18:02 ` Namhyung Kim [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=aDdPvCIYmSPXmBJG@google.com \
    --to=namhyung@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alex.gaynor@gmail.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=dvyukov@google.com \
    --cc=gary@garyguo.net \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jiapeng.chong@linux.alibaba.com \
    --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=ojeda@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stephen.s.brennan@oracle.com \
    --cc=tmgross@umich.edu \
    --cc=weilin.wang@intel.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;
as well as URLs for NNTP newsgroup(s).