linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	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>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf trace: Fix some more memory leaks
Date: Thu, 8 May 2025 10:36:19 -0700	[thread overview]
Message-ID: <aBzrkz0__S_eupgB@google.com> (raw)
In-Reply-To: <aBzFGKKubskQDLrs@x1>

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@toolbx 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@toolbx 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


  reply	other threads:[~2025-05-08 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 20:27 [PATCH v1] perf trace: Fix some more memory leaks Ian Rogers
2025-04-02  1:16 ` Howard Chu
2025-05-08 14:52 ` Arnaldo Carvalho de Melo
2025-05-08 17:36   ` Namhyung Kim [this message]
2025-05-08 20:11     ` Arnaldo Carvalho de Melo
2025-05-09 15:47       ` Namhyung Kim

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=aBzrkz0__S_eupgB@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.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=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).