[tip:tracing/urgent] ring-buffer: Fix memleak in ring_buffer_free()

[tip-bot for Eric Dumazet]

Commit-ID:  bd3f02212d6a457267e0c9c02c426151c436d9d4
Gitweb:     http://git.kernel.org/tip/bd3f02212d6a457267e0c9c02c426151c436d9d4
Author:     Eric Dumazet <eric.dumazet@xxxxxxxxx>
AuthorDate: Fri, 7 Aug 2009 12:49:29 +0200
Committer:  Steven Rostedt <rostedt@xxxxxxxxxxx>
CommitDate: Fri, 7 Aug 2009 12:46:39 -0400

ring-buffer: Fix memleak in ring_buffer_free()

I noticed oprofile memleaked in linux-2.6 current tree,
and tracked this ring-buffer leak.

Signed-off-by: Eric Dumazet <eric.dumazet@xxxxxxxxx>
LKML-Reference: <4A7C06B9.2090302@xxxxxxxxx>
Cc: stable@xxxxxxxxxx
Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx>


---
 kernel/trace/ring_buffer.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
index d4d3580..a330513 100644
--- a/kernel/trace/ring_buffer.c
+++ b/kernel/trace/ring_buffer.c
@@ -735,6 +735,7 @@ ring_buffer_free(struct ring_buffer *buffer)
 
 	put_online_cpus();
 
+	kfree(buffer->buffers);
 	free_cpumask_var(buffer->cpumask);
 
 	kfree(buffer);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/