From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: [PATCH v2 0/4] perf timechart: Fix memory leaks
Date: Fri, 5 Jun 2026 16:51:27 -0700 [thread overview]
Message-ID: <20260605235131.2440270-1-namhyung@kernel.org> (raw)
Hello,
This patchset fixes memory leaks in the perf timechart code.
I've extended and verified the timechart test with ASAN.
v2)
* use zfree() and explicit clear for potential misuse (Arnaldo)
* fix a wrong condition in the draw_wakeups() (Sashiko)
* move misplaced hunk in the second commit to the first
While it doesn't depend on my other timechart patch series [1], fixing
the memory leaks entirely requires some work there. So I'd suggest
applying this after the previous work.
Thanks,
Namhyung
[1] https://lore.kernel.org/r/20260604214931.2202322-1-namhyung@kernel.org
Namhyung Kim (4):
perf timechart: Release event samples at the end
perf timechart: Fix memory leaks during record
perf timechart: Fix memory leaks in draw_wakeups()
perf test: Update perf timechart test
tools/perf/builtin-timechart.c | 105 ++++++++++++++++++++++++----
tools/perf/tests/shell/timechart.sh | 24 ++++---
2 files changed, 106 insertions(+), 23 deletions(-)
--
2.54.0.1032.g2f8565e1d1-goog
next reply other threads:[~2026-06-05 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 23:51 Namhyung Kim [this message]
2026-06-05 23:51 ` [PATCH v2 1/4] perf timechart: Release event samples at the end Namhyung Kim
2026-06-06 0:05 ` sashiko-bot
2026-06-05 23:51 ` [PATCH v2 2/4] perf timechart: Fix memory leaks during record Namhyung Kim
2026-06-05 23:51 ` [PATCH v2 3/4] perf timechart: Fix memory leaks in draw_wakeups() Namhyung Kim
2026-06-05 23:51 ` [PATCH v2 4/4] perf test: Update perf timechart test 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=20260605235131.2440270-1-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--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