[for-next][PATCH 13/29] tracing: No need to free iter->trace in fail path of tracing_open_pipe()

From: Steven Rostedt
Date: Wed Feb 20 2019 - 13:39:48 EST


From: "zhangyi (F)" <yi.zhang@xxxxxxxxxx>

Commit d716ff71dd12 ("tracing: Remove taking of trace_types_lock in
pipe files") use the current tracer instead of the copy in
tracing_open_pipe(), but it forget to remove the freeing sentence in
the error path.

[ Note, this is harmless because kfree(NULL) is allowed and iter is
allocated with kzalloc() making iter->trace = NULL -- S. Rostedt ]

Link: http://lkml.kernel.org/r/1550060946-45984-1-git-send-email-yi.zhang@xxxxxxxxxx

Fixes: d716ff71dd12 ("tracing: Remove taking of trace_types_lock in pipe files")
Signed-off-by: zhangyi (F) <yi.zhang@xxxxxxxxxx>
Signed-off-by: Steven Rostedt (VMware) <rostedt@xxxxxxxxxxx>
---
kernel/trace/trace.c | 1 -
1 file changed, 1 deletion(-)

diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index c521b7347482..b583ff7656bb 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -5624,7 +5624,6 @@ static int tracing_open_pipe(struct inode *inode, struct file *filp)
return ret;

fail:
- kfree(iter->trace);
kfree(iter);
__trace_array_put(tr);
mutex_unlock(&trace_types_lock);
--
2.20.1