[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174293217194.2401011.17122687947274846781.b4-ty@kernel.org>
Date: Tue, 25 Mar 2025 12:49:31 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>,
Ian Rogers <irogers@...gle.com>, Kan Liang <kan.liang@...ux.intel.com>,
Namhyung Kim <namhyung@...nel.org>
Cc: Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, linux-perf-users@...r.kernel.org,
Ravi Bangoria <ravi.bangoria@....com>
Subject: Re: [PATCH] perf report: Fix a memory leak for perf_env on AMD
On Mon, 10 Mar 2025 17:04:16 -0700, Namhyung Kim wrote:
> The env.pmu_mapping can be leaked when it reads data from a pipe on AMD.
> For a pipe data, it reads the header data including pmu_mapping from
> PERF_RECORD_HEADER_FEATURE runtime. But it's already set in:
>
> perf_session__new()
> __perf_session__new()
> evlist__init_trace_event_sample_raw()
> evlist__has_amd_ibs()
> perf_env__nr_pmu_mappings()
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists