From: Namhyung Kim <namhyung@kernel.org>
To: Tanushree Shah <tshah@linux.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
jolsa@kernel.org, adrian.hunter@intel.com, vmolnaro@redhat.com,
mpetlan@redhat.com, tmricht@linux.ibm.com, maddy@linux.ibm.com,
irogers@google.com, 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: Fri, 3 Jul 2026 16:59:51 -0700 [thread overview]
Message-ID: <akhM9-d-tNjZzb-A@google.com> (raw)
In-Reply-To: <bf12f3d6-7410-44da-b4c4-32dc21244a12@linux.ibm.com>
On Thu, Jul 02, 2026 at 12:46:54PM +0530, Tanushree Shah wrote:
> Hi Namhyung,
>
> Yes, I was planning to send a v2 based on the review comments to fix the
> pre-existing issue.
>
> However, Arnaldo mentioned that the original patch had already been merged
> before I got to send a v2, so I addressed the pre-existing issue in a
> separate patch instead. The patch is available here:
>
> https://lore.kernel.org/linux-perf-users/20260606121528.406919-2-tshah@linux.ibm.com/
>
> That said, although Arnaldo mentioned that this patch had been merged, I
> don't see it in perf-tools-next yet either. I'll wait for him to clarify its
> current status.
It's not in the perf-tools-next, and no plan to add it. Please send v2.
Thanks,
Namhyung
next prev parent reply other threads:[~2026-07-03 23:59 UTC|newest]
Thread overview: 11+ 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 7:06 ` sashiko-bot
2026-06-04 16:10 ` Tanushree Shah
2026-06-04 21:29 ` Arnaldo Carvalho de Melo
2026-06-11 11:53 ` Tanushree Shah
2026-07-01 21:20 ` Namhyung Kim
2026-07-02 7:16 ` Tanushree Shah
2026-07-03 23:59 ` Namhyung Kim [this message]
2026-07-07 14:06 ` Tanushree Shah
2026-07-08 6:05 ` Namhyung Kim
2026-07-08 19:25 ` 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=akhM9-d-tNjZzb-A@google.com \
--to=namhyung@kernel.org \
--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=tmricht@linux.ibm.com \
--cc=tshah@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 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.