From: Chunyu Hu <[email protected]>

commit d39cdd2036a6 ("tracing: Make tracer_flags use the right set_flag
callback")  introduces a potential mutex deadlock issue, as it forgets to
free the mutex when allocaing the tracer_flags gets fail.

The issue was found by Dan Carpenter through Smatch static code check tool.

Link: 
http://lkml.kernel.org/r/[email protected]

Fixes: d39cdd2036a6 ("tracing: Make tracer_flags use the right set_flag 
callback")
Reported-by: Dan Carpenter <[email protected]>
Signed-off-by: Chunyu Hu <[email protected]>
Signed-off-by: Steven Rostedt <[email protected]>
---
 kernel/trace/trace.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index b401a1892dc6..0ae46048f724 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1256,8 +1256,10 @@ int __init register_tracer(struct tracer *type)
        if (!type->flags) {
                /*allocate a dummy tracer_flags*/
                type->flags = kmalloc(sizeof(*type->flags), GFP_KERNEL);
-               if (!type->flags)
-                       return -ENOMEM;
+               if (!type->flags) {
+                       ret = -ENOMEM;
+                       goto out;
+               }
                type->flags->val = 0;
                type->flags->opts = dummy_tracer_opt;
        } else
-- 
2.7.0


Reply via email to