public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Weigang He <geoffreyhe2@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2] scripts/tracepoint-update: fix memory leak in add_string() on failure
Date: Wed, 21 Jan 2026 11:22:53 +0900	[thread overview]
Message-ID: <20260121112253.3e02bd1ebb50ad6d1651bb1f@kernel.org> (raw)
In-Reply-To: <20260119114542.1714405-1-geoffreyhe2@gmail.com>

On Mon, 19 Jan 2026 11:45:42 +0000
Weigang He <geoffreyhe2@gmail.com> wrote:

> When realloc() fails in add_string(), the function returns -1 but leaves
> *vals pointing to the previously allocated memory. This can cause memory
> leaks in callers like make_trace_array() that return on error without
> freeing the partially built array.
> 
> Fix this by freeing *vals and setting it to NULL when realloc() fails.
> This makes the error handling self-contained in add_string() so callers
> don't need to handle cleanup on failure.

This looks not enough. If the memory allocation is failed, it should NOT
continue anything.

I think we need to make the command itself failure when it fails to
allocate memory, as below:

diff --git a/scripts/tracepoint-update.c b/scripts/tracepoint-update.c
index 90046aedc97b..1b4129a21942 100644
--- a/scripts/tracepoint-update.c
+++ b/scripts/tracepoint-update.c
@@ -94,7 +94,7 @@ static void make_trace_array(struct elf_tracepoint *etrace)
 		if (!len)
 			continue;
 		if (add_string(str, &vals, &count) < 0)
-			return;
+			exit(EXIT_FAILURE);
 	}
 
 	/* If CONFIG_TRACEPOINT_VERIFY_USED is not set, there's nothing to do */


Thank you,

> 
> This bug is found by my static analysis tool and my code review.
> 
> Signed-off-by: Weigang He <geoffreyhe2@gmail.com>
> ---
>  scripts/tracepoint-update.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/scripts/tracepoint-update.c b/scripts/tracepoint-update.c
> index 90046aedc97b9..5cf43c0aac891 100644
> --- a/scripts/tracepoint-update.c
> +++ b/scripts/tracepoint-update.c
> @@ -49,6 +49,8 @@ static int add_string(const char *str, const char ***vals, int *count)
>  		array = realloc(array, sizeof(char *) * size);
>  		if (!array) {
>  			fprintf(stderr, "Failed memory allocation\n");
> +			free(*vals);
> +			*vals = NULL;
>  			return -1;
>  		}
>  		*vals = array;
> -- 
> 2.34.1
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  parent reply	other threads:[~2026-01-21  2:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 11:45 [PATCH v2] scripts/tracepoint-update: fix memory leak in add_string() on failure Weigang He
2026-01-20 10:00 ` Markus Elfring
2026-01-21  2:22 ` Masami Hiramatsu [this message]
2026-01-23 17:42   ` Steven Rostedt

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=20260121112253.3e02bd1ebb50ad6d1651bb1f@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=geoffreyhe2@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.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