From: Namhyung Kim <namhyung@kernel.org>
To: 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>,
Michalis Niarchos <michael.niarchos@gmail.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] perf kvm: Fix memory leaks
Date: Wed, 12 Aug 2026 14:07:58 -0700 [thread overview]
Message-ID: <178656887896.4021779.4825437848306350814.b4-ty@kernel.org> (raw)
In-Reply-To: <20260807-perf-kvm-leaks-v1-0-7b5e2f97905a@gmail.com>
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
> #3 0x55f42782dab7 in handle_kvm_event /home/mike/git/linux/tools/perf/builtin-kvm.c:950
> #4 0x55f42782fa80 in process_sample_event /home/mike/git/linux/tools/perf/builtin-kvm.c:1159
> ...
> #14 0x55f42783236c in read_events /home/mike/git/linux/tools/perf/builtin-kvm.c:1591
> #15 0x55f4278326f8 in kvm_events_report_vcpu /home/mike/git/linux/tools/perf/builtin-kvm.c:1636
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
next prev parent reply other threads:[~2026-08-12 21:07 UTC|newest]
Thread overview: 9+ 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 ` Michalis Niarchos
2026-08-07 15:08 ` [PATCH 1/2] perf kvm: Fix memory leak in process_sample_event() Michalis Niarchos via B4 Relay
2026-08-07 15:08 ` Michalis Niarchos
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-07 15:08 ` Michalis Niarchos
2026-08-12 21:07 ` Namhyung Kim [this message]
2026-08-13 20:15 ` [PATCH 0/2] perf kvm: Fix memory leaks Michalis Niarchos
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=178656887896.4021779.4825437848306350814.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--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=michael.niarchos@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.