From: Michalis Niarchos <michael.niarchos@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] perf kvm: Fix memory leaks
Date: Thu, 13 Aug 2026 22:15:05 +0200 [thread overview]
Message-ID: <6C786771-AFE9-4DB9-A5A2-DC3D024488B5@gmail.com> (raw)
In-Reply-To: <178656887896.4021779.4825437848306350814.b4-ty@kernel.org>
On August 12, 2026 11:07:58 PM GMT+02:00, Namhyung Kim <namhyung@kernel.org> wrote:
>On Fri, 07 Aug 2026 17:08:34 +0200, Michalis Niarchos wrote:
>> Running ./perf kvm stat report with ASan, revealed some memory leaks:
>>
>> ==206006==ERROR: LeakSanitizer: detected memory leaks
>>
>> Direct leak of 72 byte(s) in 3 object(s) allocated from:
>> #0 0x7ff86bf2bea9 in calloc (/usr/lib/libasan.so.8+0x12bea9) (BuildId: 7f2845989b820f536270e19ec47df085ae89a675)
>> #1 0x55f42795a0d5 in zalloc ../../lib/zalloc.c:8
>> #2 0x55f42782d7f4 in per_vcpu_record /home/mike/git/linux/tools/perf/builtin-kvm.c:929
>>
>> [...]
>Applied to perf-tools-next, thanks!
>
>Best regards,
>Namhyung
>
Thanks for reviewing and applying!
Kind regards,
Michalis
prev parent reply other threads:[~2026-08-13 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 15:08 [PATCH 0/2] perf kvm: Fix memory leaks Michalis Niarchos via B4 Relay
2026-08-07 15:08 ` [PATCH 1/2] perf kvm: Fix memory leak in process_sample_event() Michalis Niarchos via B4 Relay
2026-08-12 7:41 ` Namhyung Kim
2026-08-07 15:08 ` [PATCH 2/2] perf kvm: Fix memory leak in cmd_kvm() Michalis Niarchos via B4 Relay
2026-08-12 21:07 ` [PATCH 0/2] perf kvm: Fix memory leaks Namhyung Kim
2026-08-13 20:15 ` Michalis Niarchos [this message]
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=6C786771-AFE9-4DB9-A5A2-DC3D024488B5@gmail.com \
--to=michael.niarchos@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@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