From: Swapnil Sapkal <swapnil.sapkal@amd.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
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: Re: [PATCH v2 0/3] perf sched stats: Fix memory leaks
Date: Wed, 15 Jul 2026 23:31:59 +0530 [thread overview]
Message-ID: <6e0e6934-2b81-43f3-bea8-bb74656edc5c@amd.com> (raw)
In-Reply-To: <20260713234536.2280374-1-namhyung@kernel.org>
Hello Namhyung,
On 14-07-2026 05:15, Namhyung Kim wrote:
> Hello,
>
> This is a small series to fix memory leaks in the perf sched stats.
> I've tested the changes with the address sanitizer.
>
Reviewed-and-tested-by: Swapnil Sapkal <swapnil.sapkal@amd.com>
> v2 changes)
> * remove invalid file closing (Sashiko)
>
>
> Thanks,
> Namhyung
>
>
> Namhyung Kim (3):
> perf sched: Add missing perf_session__delete()
> perf sched: Fix memory leaks in perf sched stats report
> perf sched: Free subcommand string after perf sched stats
>
> tools/perf/builtin-sched.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
--
Thanks and Regards,
Swapnil
next prev parent reply other threads:[~2026-07-15 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 23:45 Namhyung Kim
2026-07-13 23:45 ` [PATCH v2 1/3] perf sched: Add missing perf_session__delete() Namhyung Kim
2026-07-13 23:45 ` [PATCH v2 2/3] perf sched: Fix memory leaks in perf sched stats report Namhyung Kim
2026-07-13 23:45 ` [PATCH v2 3/3] perf sched: Free subcommand string after perf sched stats Namhyung Kim
2026-07-15 18:01 ` Swapnil Sapkal [this message]
2026-07-16 16:58 ` [PATCH v2 0/3] perf sched stats: Fix memory leaks 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=6e0e6934-2b81-43f3-bea8-bb74656edc5c@amd.com \
--to=swapnil.sapkal@amd.com \
--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=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