tracing: Fix leak of ring buffer data when new instances creation fails
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>
Fri, 6 Jun 2014 04:01:46 +0000 (00:01 -0400)
committerSteven Rostedt <rostedt@goodmis.org>
Fri, 6 Jun 2014 08:53:40 +0000 (04:53 -0400)
commit23aaa3c18e33fe048671b419781b5e44175efafe
tree03a3129a3bf0b04061d2904789a87c668de755c6
parent748ec3a20eb44fce19af3cef04f8db8a8e7aead3
tracing: Fix leak of ring buffer data when new instances creation fails

Yoshihiro Yunomae reported that the ring buffer data for a trace
instance does not get properly cleaned up when it fails. He proposed
a patch that manually cleaned the data up and addad a bunch of labels.
The labels are not needed because all trace array is allocated with
a kzalloc which initializes it to 0 and all kfree()s can take a NULL
pointer and will ignore it.

Adding a new helper function free_trace_buffers() that can also take
null buffers to free the buffers that were allocated by
allocate_trace_buffers().

Link: http://lkml.kernel.org/r/20140605223522.32311.31664.stgit@yunodevel
Reported-by: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
kernel/trace/trace.c