From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1 4/5] perf trace: Free the host machine allocation
Date: Fri, 18 Sep 2026 06:45:44 +0000 [thread overview]
Message-ID: <20260918064544.8A4B31F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918063249.2172589-5-irogers@google.com>
> trace__symbols_init() creates the host machine with machine__new_host(),
> which allocates a struct machine, but trace__symbols__exit() released it
> with machine__exit(). That tears down the contents of the machine and
> leaves the allocation itself behind, so use machine__delete(), which
> does both. The replay path points trace->host at the machine embedded in
> the session and never reaches here, so nothing else is affected.
>
> The leak was hidden from leak sanitizer because trace__symbols_init()
> passes the machine to trace_event__register_resolver(), which stores it
> as the private pointer of the global tep handle. The handle kept the
> machine reachable for as long as the process lived, so it was only once
> the handle started being freed that this was reported:
>
> Direct leak of 1256 byte(s) in 1 object(s) allocated from:
> #1 __machine__new_host util/machine.c:135
> #2 machine__new_host util/machine.c:155
> #3 trace__symbols_init builtin-trace.c:2105
> #4 trace__run builtin-trace.c:4759
> #5 cmd_trace builtin-trace.c:6091
>
> Assisted-by: Antigravity:gemini-3.1-pro
> Signed-off-by: Ian Rogers <irogers@google.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260918063249.2172589-1-irogers@google.com?part=4
next prev parent reply other threads:[~2026-09-18 6:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 6:32 [PATCH v1 0/5] perf trace: Tracepoint format error handling and leak fixes Ian Rogers
2026-09-18 6:32 ` [PATCH v1 1/5] perf trace-event: Report tracepoint format errors with NULL and errno Ian Rogers
2026-09-18 6:41 ` sashiko-bot
2026-09-18 6:32 ` [PATCH v1 2/5] perf trace-event: Reuse an already parsed tracepoint format Ian Rogers
2026-09-18 6:38 ` sashiko-bot
2026-09-18 6:32 ` [PATCH v1 3/5] perf trace-event: Free the global trace_event when a command ends Ian Rogers
2026-09-18 6:41 ` sashiko-bot
2026-09-18 6:32 ` [PATCH v1 4/5] perf trace: Free the host machine allocation Ian Rogers
2026-09-18 6:45 ` sashiko-bot [this message]
2026-09-18 6:32 ` [PATCH v1 5/5] perf thread: Free the comm read from procfs Ian Rogers
2026-09-18 6:38 ` sashiko-bot
2026-09-25 13:00 ` [PATCH v1 0/5] perf trace: Tracepoint format error handling and leak fixes Arnaldo Carvalho de Melo
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=20260918064544.8A4B31F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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