[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z04u-7DQr5w9daS5@google.com>
Date: Mon, 2 Dec 2024 14:04:43 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Zhongqiu Han <quic_zhonhan@...cinc.com>
Cc: peterz@...radead.org, mingo@...hat.com, acme@...nel.org,
mark.rutland@....com, alexander.shishkin@...ux.intel.com,
jolsa@...nel.org, irogers@...gle.com, adrian.hunter@...el.com,
kan.liang@...ux.intel.com, james.clark@...aro.org,
yangyicong@...ilicon.com, song@...nel.org,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
bpf@...r.kernel.org
Subject: Re: [PATCH 0/3] perf tool: Fix multiple memory leakages
On Thu, Nov 28, 2024 at 08:54:29PM +0800, Zhongqiu Han wrote:
> Fix memory leakages when btf_node or bpf_prog_info_node is duplicated
> during insertion into perf_env.
>
> Signed-off-by: Zhongqiu Han <quic_zhonhan@...cinc.com>
> ---
> Zhongqiu Han (3):
> perf header: Fix one memory leakage in process_bpf_btf()
> perf header: Fix one memory leakage in process_bpf_prog_info()
> perf bpf: Fix two memory leakages when calling
> perf_env__insert_bpf_prog_info()
Although I have a nitpick in the patch 3, it looks good otherwise.
Reviewed-by: Namhyung Kim <namhyung@...nel.org>
And I don't think the Fixes tags are correct, but it won't apply before
the change it points to. So for practical reason, I'm ok with that.
Thanks,
Namhyung
>
> tools/perf/util/bpf-event.c | 10 ++++++++--
> tools/perf/util/env.c | 12 ++++++++----
> tools/perf/util/env.h | 4 ++--
> tools/perf/util/header.c | 8 ++++++--
> 4 files changed, 24 insertions(+), 10 deletions(-)
>
>
> base-commit: f486c8aa16b8172f63bddc70116a0c897a7f3f02
> --
> 2.25.1
>
Powered by blists - more mailing lists