[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aBzrkz0__S_eupgB@google.com>
Date: Thu, 8 May 2025 10:36:19 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Ian Rogers <irogers@...gle.com>, Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] perf trace: Fix some more memory leaks
On Thu, May 08, 2025 at 11:52:08AM -0300, Arnaldo Carvalho de Melo wrote:
> On Tue, Apr 01, 2025 at 01:27:15PM -0700, Ian Rogers wrote:
> > The files.max is the maximum valid fd in the files array and so
> > freeing the values needs to be inclusive of the max value.
> >
> > Add missing thread__put of the found parent thread in
> > thread__e_machine.
>
> Split it into:
>
> ⬢ [acme@...lbx perf-tools-next]$ git log --oneline -2
> 7900938850645ed4 (HEAD -> perf-tools-next) perf trace: Add missing thread__put() in thread__e_machine()
> 8830091383b03498 perf trace: Free the files.max entry in files->table
> ⬢ [acme@...lbx perf-tools-next]$
>
> So that git --oneline is more descriptive, etc.
>
> Thanks, applied to perf-tools-next,
PTAL this one as well.
https://lore.kernel.org/r/20250403054213.7021-1-namhyung@kernel.org
Thanks,
Namhyung
Powered by blists - more mailing lists