All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Markus Elfring <Markus.Elfring@web.de>
Subject: Re: [PATCH] tracing: Cleanup event_enable_trigger_parse() by using __free()
Date: Thu, 2 Jul 2026 07:41:19 +0900	[thread overview]
Message-ID: <20260702074119.cc576d8423ed766fb407f7cb@kernel.org> (raw)
In-Reply-To: <20260701174829.67ab8a33@gandalf.local.home>

On Wed, 1 Jul 2026 17:48:29 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> From: Steven Rostedt <rostedt@goodmis.org>
> 
> The enable_data variable gets freed on most error paths in
> event_enable_trigger_parse(). Use free() to free it and just before
> returning normally, call no_free_ptr(enable_data) to keep it from being
> freed.
> 

This looks good to me.

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

Thank you,

> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
>  kernel/trace/trace_events_trigger.c | 12 ++++--------
>  1 file changed, 4 insertions(+), 8 deletions(-)
> 
> diff --git a/kernel/trace/trace_events_trigger.c b/kernel/trace/trace_events_trigger.c
> index 655db2e82513..fe5ca6ac7c8d 100644
> --- a/kernel/trace/trace_events_trigger.c
> +++ b/kernel/trace/trace_events_trigger.c
> @@ -1739,7 +1739,7 @@ int event_enable_trigger_parse(struct event_command *cmd_ops,
>  			       char *glob, char *cmd, char *param_and_filter)
>  {
>  	struct trace_event_file *event_enable_file;
> -	struct enable_trigger_data *enable_data;
> +	struct enable_trigger_data *enable_data __free(kfree) = NULL;
>  	struct event_trigger_data *trigger_data;
>  	struct trace_array *tr = file->tr;
>  	char *param, *filter;
> @@ -1789,17 +1789,13 @@ int event_enable_trigger_parse(struct event_command *cmd_ops,
>  	enable_data->file = event_enable_file;
>  
>  	trigger_data = trigger_data_alloc(cmd_ops, cmd, param, enable_data);
> -	if (!trigger_data) {
> -		kfree(enable_data);
> +	if (!trigger_data)
>  		return ret;
> -	}
>  
>  	if (remove) {
>  		event_trigger_unregister(cmd_ops, file, glob+1, trigger_data);
>  		kfree(trigger_data);
> -		kfree(enable_data);
> -		ret = 0;
> -		return ret;
> +		return 0;
>  	}
>  
>  	/* Up the trigger_data count to make sure nothing frees it on failure */
> @@ -1829,6 +1825,7 @@ int event_enable_trigger_parse(struct event_command *cmd_ops,
>  		goto out_disable;
>  
>  	event_trigger_free(trigger_data);
> +	no_free_ptr(enable_data);
>  	return ret;
>   out_disable:
>  	trace_event_enable_disable(event_enable_file, 0, 1);
> @@ -1837,7 +1834,6 @@ int event_enable_trigger_parse(struct event_command *cmd_ops,
>   out_free:
>  	event_trigger_reset_filter(cmd_ops, trigger_data);
>  	event_trigger_free(trigger_data);
> -	kfree(enable_data);
>  
>  	return ret;
>  }
> -- 
> 2.53.0
> 


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

  reply	other threads:[~2026-07-01 22:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 21:48 [PATCH] tracing: Cleanup event_enable_trigger_parse() by using __free() Steven Rostedt
2026-07-01 22:41 ` Masami Hiramatsu [this message]
2026-07-02  9:58 ` Markus Elfring
2026-07-02 20:53   ` Steven Rostedt
2026-07-03  5:00     ` Markus Elfring
2026-07-03 15:42       ` Steven Rostedt
2026-07-03 18:37         ` Markus Elfring
2026-07-03 19:09           ` Steven Rostedt
2026-07-03 19:20             ` Markus Elfring
2026-07-03 19:33               ` Steven Rostedt
2026-07-02 11:58 ` [PATCH] " Markus Elfring

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=20260702074119.cc576d8423ed766fb407f7cb@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=Markus.Elfring@web.de \
    --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 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.