* [for-next][PATCH] tracing: Fix memory leak on instance deletion
@ 2014-06-08 1:42 Steven Rostedt
0 siblings, 0 replies; only message in thread
From: Steven Rostedt @ 2014-06-08 1:42 UTC (permalink / raw)
To: LKML; +Cc: Ingo Molnar, Andrew Morton
Ug, found a memory leak in instance deletion. Missed freeing the
snapshot buffer.
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 17f83bffd1b41b5cd6fe08ad12c8a69341542ba2
Steven Rostedt (Red Hat) (1)
tracing: Fix memory leak on instance deletion
----
trace.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
---------------------------
commit a9fcaaac37b3baba1343f906f52aeb65c4d4e356
Author: Steven Rostedt (Red Hat) <rostedt@goodmis.org>
Date: Fri Jun 6 23:17:28 2014 -0400
tracing: Fix memory leak on instance deletion
When an instance is created, it also gets a snapshot ring buffer
allocated (with minimum of pages). But when it is deleted the snapshot
buffer is not. There was a helper function added to match the allocation
of these ring buffers to a way to free them, but it wasn't used by
the deletion of an instance. Using that helper function solves this
memory leak.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 26cfff38e2ab..16f7038d1f4d 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -6349,8 +6349,7 @@ static int instance_delete(const char *name)
event_trace_del_tracer(tr);
ftrace_destroy_function_files(tr);
debugfs_remove_recursive(tr->dir);
- free_percpu(tr->trace_buffer.data);
- ring_buffer_free(tr->trace_buffer.buffer);
+ free_trace_buffers(tr);
kfree(tr->name);
kfree(tr);
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-06-08 1:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-08 1:42 [for-next][PATCH] tracing: Fix memory leak on instance deletion Steven Rostedt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®