* [PATCH] tracing: Fix error handling in event_hist_trigger_parse
@ 2025-12-11 10:00 Miaoqian Lin
2025-12-12 1:45 ` Steven Rostedt
0 siblings, 1 reply; 2+ messages in thread
From: Miaoqian Lin @ 2025-12-11 10:00 UTC (permalink / raw)
To: Steven Rostedt, Masami Hiramatsu, Mathieu Desnoyers, Tom Zanussi,
linux-kernel, linux-trace-kernel
Cc: linmq006, stable
Memory allocated with trigger_data_alloc() require trigger_data_free()
for proper cleanup.
Replace kfree() with trigger_data_free() to fix this.
Found via static analysis and code review.
Fixes: e1f187d09e11 ("tracing: Have existing event_command.parse() implementations use helpers")
Cc: stable@vger.kernel.org
Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
---
kernel/trace/trace_events_hist.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
index 5e6e70540eef..f9886fff7123 100644
--- a/kernel/trace/trace_events_hist.c
+++ b/kernel/trace/trace_events_hist.c
@@ -6902,7 +6902,7 @@ static int event_hist_trigger_parse(struct event_command *cmd_ops,
remove_hist_vars(hist_data);
- kfree(trigger_data);
+ trigger_data_free(trigger_data);
destroy_hist_data(hist_data);
goto out;
--
2.25.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] tracing: Fix error handling in event_hist_trigger_parse
2025-12-11 10:00 [PATCH] tracing: Fix error handling in event_hist_trigger_parse Miaoqian Lin
@ 2025-12-12 1:45 ` Steven Rostedt
0 siblings, 0 replies; 2+ messages in thread
From: Steven Rostedt @ 2025-12-12 1:45 UTC (permalink / raw)
To: Miaoqian Lin
Cc: Masami Hiramatsu, Mathieu Desnoyers, Tom Zanussi, linux-kernel,
linux-trace-kernel, stable
On Thu, 11 Dec 2025 14:00:58 +0400
Miaoqian Lin <linmq006@gmail.com> wrote:
> @@ -6902,7 +6902,7 @@ static int event_hist_trigger_parse(struct event_command *cmd_ops,
>
> remove_hist_vars(hist_data);
>
> - kfree(trigger_data);
> + trigger_data_free(trigger_data);
>
> destroy_hist_data(hist_data);
> goto out;
The above code has this:
out_free:
event_trigger_reset_filter(cmd_ops, trigger_data);
remove_hist_vars(hist_data);
kfree(trigger_data);
destroy_hist_data(hist_data);
goto out;
Where we have;
void event_trigger_reset_filter(struct event_command *cmd_ops,
struct event_trigger_data *trigger_data)
{
if (cmd_ops->set_filter)
cmd_ops->set_filter(NULL, trigger_data, NULL);
}
And trigger_data_free() starts with:
void trigger_data_free(struct event_trigger_data *data)
{
if (data->cmd_ops->set_filter)
data->cmd_ops->set_filter(NULL, data, NULL);
thus it looks like the current code is an open coded version of
trigger_data_free() without synchronization (as it isn't needed here).
Thus, I believe this is more of a clean up and not a fix (something to
go into the next merge window and not the current -rc release).
And the code can be changed to also remove the event_trigger_reset_filter()
call.
-- Steve
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-12-12 1:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-12-11 10:00 [PATCH] tracing: Fix error handling in event_hist_trigger_parse Miaoqian Lin
2025-12-12 1:45 ` Steven Rostedt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).