From: Tanushree Shah <tshah@linux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: jolsa@kernel.org, adrian.hunter@intel.com, vmolnaro@redhat.com,
mpetlan@redhat.com, tmricht@linux.ibm.com, maddy@linux.ibm.com,
irogers@google.com, namhyung@kernel.org,
linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
atrajeev@linux.ibm.com, hbathini@linux.ibm.com,
Tejas.Manhas1@ibm.com, Tanushree.Shah@ibm.com,
Shivani.Nittor@ibm.com
Subject: Re: [PATCH] perf data convert json: Fix trace_seq memory leak in process_sample_event()
Date: Thu, 11 Jun 2026 17:23:45 +0530 [thread overview]
Message-ID: <f6937d04-6346-443b-8054-6f8a801a4fd8@linux.ibm.com> (raw)
In-Reply-To: <aiHuIBAIgv3L6TI7@x1>
Hello Arnaldo
Thanks for checking the patch. I cannot see this patch applied on
perf-tools-next yet.
https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/log/?h=perf-tools-next
Thanks.
On 05/06/26 02:59, Arnaldo Carvalho de Melo wrote:
> On Thu, Jun 04, 2026 at 12:25:19PM +0530, Tanushree Shah wrote:
>> Unlike the in-kernel trace_seq which uses a statically allocated buffer,
>> the userspace traceevent library's trace_seq uses a dynamically allocated
>> one. Therefore, every trace_seq_init() call must be paired with a
>> trace_seq_destroy(), otherwise it produces a memory leak.
>>
>> In process_sample_event(), a trace_seq is initialized for each field when
>> formatting tracepoint raw_data, but the matching trace_seq_destroy() is
>> never called, leaking memory for every field of every sample processed.
>>
>> Add the missing trace_seq_destroy() after using the trace_seq buffer to
>> properly free the allocated memory.
>>
>> Detected with Valgrind on a perf.data file with 2,729 tracepoint samples:
>> Before: definitely lost: 55,537,664 bytes in 13,559 blocks
>> After: definitely lost: 0 bytes in 0 blocks
>
> Thanks, applied to perf-tools-next, for v7.2.
>
> - Arnaldo
>
>> Fixes: 9d895e468429 ("perf data: Add tracepoint fields when converting to JSON")
>> Signed-off-by: Tanushree Shah <tshah@linux.ibm.com>
>> ---
>> tools/perf/util/data-convert-json.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/tools/perf/util/data-convert-json.c b/tools/perf/util/data-convert-json.c
>> index d526c91312ed..6dd9349ab10f 100644
>> --- a/tools/perf/util/data-convert-json.c
>> +++ b/tools/perf/util/data-convert-json.c
>> @@ -257,6 +257,7 @@ static int process_sample_event(const struct perf_tool *tool,
>> trace_seq_init(&s);
>> tep_print_field(&s, sample->raw_data, fields[i]);
>> output_json_key_string(out, true, 3, fields[i]->name, s.buffer);
>> + trace_seq_destroy(&s);
>>
>> i++;
>> }
>> --
>> 2.47.3
prev parent reply other threads:[~2026-06-11 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 6:55 [PATCH] perf data convert json: Fix trace_seq memory leak in process_sample_event() Tanushree Shah
2026-06-04 21:29 ` Arnaldo Carvalho de Melo
2026-06-11 11:53 ` Tanushree Shah [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=f6937d04-6346-443b-8054-6f8a801a4fd8@linux.ibm.com \
--to=tshah@linux.ibm.com \
--cc=Shivani.Nittor@ibm.com \
--cc=Tanushree.Shah@ibm.com \
--cc=Tejas.Manhas1@ibm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=atrajeev@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=tmricht@linux.ibm.com \
--cc=vmolnaro@redhat.com \
/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