From: Steven Rostedt <rostedt@goodmis.org>
To: Shang XiaoJing <shangxiaojing@huawei.com>
Cc: <acme@redhat.com>, <linux-kernel@vger.kernel.org>, <namhyung@kernel.org>
Subject: Re: [PATCH] tools lib traceevent: Fix double free in event_read_fields()
Date: Thu, 20 Oct 2022 17:23:24 -0400 [thread overview]
Message-ID: <20221020172324.66c6927f@gandalf.local.home> (raw)
In-Reply-To: <20221017085937.8583-1-shangxiaojing@huawei.com>
On Mon, 17 Oct 2022 16:59:37 +0800
Shang XiaoJing <shangxiaojing@huawei.com> wrote:
> There is a double free in event_read_fields(). After calling free_token()
> to free the token, if append() failed, then goto fail, which will call
> free_token() again. Triggered by compiling with perf and run "perf sched
> record". Fix the double free by goto fail_expect instead of fail while
> append() failed, which won't call redundant free_token().
>
> BUG: double free
> free(): double free detected in tcache 2
> Aborted
>
> Fixes: d286447f23cd ("tools lib traceevent: Handle realloc() failure path")
> Signed-off-by: Shang XiaoJing <shangxiaojing@huawei.com>
> ---
> tools/lib/traceevent/event-parse.c | 2 +-
tool/lib/traceevent is deprecated.
Can you send this patch to linux-trace-devel@vger.kernel.org against
https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/
Thanks!
-- Steve
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/lib/traceevent/event-parse.c b/tools/lib/traceevent/event-parse.c
> index 8e24c4c78c7f..e0a5a22fe702 100644
> --- a/tools/lib/traceevent/event-parse.c
> +++ b/tools/lib/traceevent/event-parse.c
> @@ -1594,7 +1594,7 @@ static int event_read_fields(struct tep_event *event, struct tep_format_field **
> ret = append(&brackets, "", "]");
> if (ret < 0) {
> free(brackets);
> - goto fail;
> + goto fail_expect;
> }
>
> /* add brackets to type */
next prev parent reply other threads:[~2022-10-20 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 8:59 Shang XiaoJing
2022-10-20 21:23 ` Steven Rostedt [this message]
2022-10-21 1:01 ` shangxiaojing
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=20221020172324.66c6927f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=shangxiaojing@huawei.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
all inboxes | Powered by JetHome®