From: Steven Rostedt Date: Mon, 12 May 2008 19:20:56 +0000 (+0200) Subject: ftrace: fix mutex unlock in trace output X-Git-Tag: v2.6.27-rc1~1102^2^2~1^2~64 X-Git-Url: http://pilppa.com/gitweb/?a=commitdiff_plain;h=d15f57f23eaba975309a153b23699cd0c0236974;p=linux-2.6-omap-h63xx.git ftrace: fix mutex unlock in trace output If the trace output changes on reading the trace files, there is a chance that the start function will return NULL. If the start function of a sequence returns NULL the stop equivalent is not called. In this case, all locks that are taken must be released even if they are released in the stop function. This patch fixes a case that a mutex was not released on return of NULL in the start sequence function. Signed-off-by: Steven Rostedt Signed-off-by: Ingo Molnar Signed-off-by: Thomas Gleixner --- diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c index 3009aafa4dd..ea11f4ebfae 100644 --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -964,8 +964,10 @@ static void *s_start(struct seq_file *m, loff_t *pos) mutex_lock(&trace_types_lock); - if (!current_trace || current_trace != iter->trace) + if (!current_trace || current_trace != iter->trace) { + mutex_unlock(&trace_types_lock); return NULL; + } atomic_inc(&trace_record_cmdline_disabled);