diff options
author | Steven Rostedt (Red Hat) <rostedt@goodmis.org> | 2016-06-17 20:10:42 (GMT) |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2016-06-20 13:46:12 (GMT) |
commit | 70c8217acd4383e069fe1898bbad36ea4fcdbdcc (patch) | |
tree | 4bf9451f8719b199f7a94d3cc7fa3b05409647ea /crypto | |
parent | 5edb56491d4812c42175980759da53388e5d86f5 (diff) | |
download | linux-70c8217acd4383e069fe1898bbad36ea4fcdbdcc.tar.xz |
tracing: Handle NULL formats in hold_module_trace_bprintk_format()
If a task uses a non constant string for the format parameter in
trace_printk(), then the trace_printk_fmt variable is set to NULL. This
variable is then saved in the __trace_printk_fmt section.
The function hold_module_trace_bprintk_format() checks to see if duplicate
formats are used by modules, and reuses them if so (saves them to the list
if it is new). But this function calls lookup_format() that does a strcmp()
to the value (which is now NULL) and can cause a kernel oops.
This wasn't an issue till 3debb0a9ddb ("tracing: Fix trace_printk() to print
when not using bprintk()") which added "__used" to the trace_printk_fmt
variable, and before that, the kernel simply optimized it out (no NULL value
was saved).
The fix is simply to handle the NULL pointer in lookup_format() and have the
caller ignore the value if it was NULL.
Link: http://lkml.kernel.org/r/1464769870-18344-1-git-send-email-zhengjun.xing@intel.com
Reported-by: xingzhen <zhengjun.xing@intel.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Fixes: 3debb0a9ddb ("tracing: Fix trace_printk() to print when not using bprintk()")
Cc: stable@vger.kernel.org # v3.5+
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions