From: Miaoqian Lin <[email protected]>

According to trigger_data_alloc() doc, trigger_data_free() should be
used to free an event_trigger_data object. This fixes a mismatch introduced
when kzalloc was replaced with trigger_data_alloc without updating
the corresponding deallocation calls.

Cc: Masami Hiramatsu <[email protected]>
Cc: Mathieu Desnoyers <[email protected]>
Cc: Tom Zanussi <[email protected]>
Link: https://lore.kernel.org/[email protected]
Fixes: e1f187d09e11 ("tracing: Have existing event_command.parse() 
implementations use helpers")
Signed-off-by: Miaoqian Lin <[email protected]>
[ SDR: Changed event_trigger_alloc/free() to trigger_data_alloc/free() ]
Signed-off-by: Steven Rostedt (Google) <[email protected]>
---
 kernel/trace/trace_events_trigger.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/kernel/trace/trace_events_trigger.c 
b/kernel/trace/trace_events_trigger.c
index dac3344ee345..c316badc608b 100644
--- a/kernel/trace/trace_events_trigger.c
+++ b/kernel/trace/trace_events_trigger.c
@@ -995,7 +995,7 @@ event_trigger_parse(struct event_command *cmd_ops,
 
        if (remove) {
                event_trigger_unregister(cmd_ops, file, glob+1, trigger_data);
-               kfree(trigger_data);
+               trigger_data_free(trigger_data);
                ret = 0;
                goto out;
        }
@@ -1022,7 +1022,7 @@ event_trigger_parse(struct event_command *cmd_ops,
 
  out_free:
        event_trigger_reset_filter(cmd_ops, trigger_data);
-       kfree(trigger_data);
+       trigger_data_free(trigger_data);
        goto out;
 }
 
-- 
2.47.2



Reply via email to