From: Tom Zanussi <zanussi@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Rosen Penev <rosenp@gmail.com>
Subject: Re: [PATCH] tracing: Do not call map->ops->elt_free() if elt_alloc() is not succeeded
Date: Tue, 26 May 2026 11:48:07 -0500 [thread overview]
Message-ID: <ba5df6966f6a8d44c3754a7ab598c5ad4060111b.camel@kernel.org> (raw)
In-Reply-To: <177933895460.108746.5396070821443932634.stgit@devnote2>
Hi Masami,
On Thu, 2026-05-21 at 13:49 +0900, Masami Hiramatsu (Google) wrote:
> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> In paths where tracing_map_elt_alloc() failed to allocate objects,
> the map->ops->elt_alloc() call was never successful. In this case,
> map->ops->elt_free() should not be called.
>
> This bug was found by Sashiko.
> Link: https://sashiko.dev/#/patchset/20260520223101.34710-1-rosenp%40gmail.com
>
> Fixes: 2734b629525a ("tracing: Add per-element variable support to tracing_map")
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> Cc: stable@vger.kernel.org
> ---
> kernel/trace/tracing_map.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/trace/tracing_map.c b/kernel/trace/tracing_map.c
> index bf1a507695b6..0dd7927df22a 100644
> --- a/kernel/trace/tracing_map.c
> +++ b/kernel/trace/tracing_map.c
> @@ -386,13 +386,11 @@ static void tracing_map_elt_init_fields(struct tracing_map_elt *elt)
> }
> }
>
> -static void tracing_map_elt_free(struct tracing_map_elt *elt)
> +static void __tracing_map_elt_free(struct tracing_map_elt *elt)
> {
> if (!elt)
> return;
>
> - if (elt->map->ops && elt->map->ops->elt_free)
> - elt->map->ops->elt_free(elt);
> kfree(elt->fields);
> kfree(elt->vars);
> kfree(elt->var_set);
> @@ -400,6 +398,17 @@ static void tracing_map_elt_free(struct tracing_map_elt *elt)
> kfree(elt);
> }
>
> +static void tracing_map_elt_free(struct tracing_map_elt *elt)
> +{
> + if (!elt)
> + return;
> +
> + /* Only objects initialized with alloc_elt() should be passed to free_elt().*/
> + if (elt->map->ops && elt->map->ops->elt_free)
> + elt->map->ops->elt_free(elt);
> + __tracing_map_elt_free(elt);
> +}
> +
> static struct tracing_map_elt *tracing_map_elt_alloc(struct tracing_map *map)
> {
> struct tracing_map_elt *elt;
> @@ -444,7 +453,7 @@ static struct tracing_map_elt *tracing_map_elt_alloc(struct tracing_map *map)
> }
> return elt;
> free:
> - tracing_map_elt_free(elt);
> + __tracing_map_elt_free(elt);
>
> return ERR_PTR(err);
> }
>
>
Looks good to me. Thanks for fixing it!
Reviewed-by: Tom Zanussi <zanussi@kernel.org>
prev parent reply other threads:[~2026-05-26 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 22:31 [PATCH] trace: allocate fields with elt struct Rosen Penev
2026-05-21 4:48 ` Masami Hiramatsu
2026-05-21 4:49 ` [PATCH] tracing: Do not call map->ops->elt_free() if elt_alloc() is not succeeded Masami Hiramatsu (Google)
2026-05-26 16:48 ` Tom Zanussi [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=ba5df6966f6a8d44c3754a7ab598c5ad4060111b.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rosenp@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.intel.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