tracing: Use pr_err() instead of WARN() for memory failures
authorSteven Rostedt (VMware) <rostedt@goodmis.org>
Sat, 25 Jan 2020 15:52:30 +0000 (10:52 -0500)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Sat, 25 Jan 2020 15:52:30 +0000 (10:52 -0500)
commit24589e3a20876dc07c62f45c8f8f8266dd39ba38
tree731bd14092dae05d75a635c4a0bbca5f65dd63ed
parent28394da25888168df379c40910591b95e8e449f7
tracing: Use pr_err() instead of WARN() for memory failures

As warnings can trigger panics, especially when "panic_on_warn" is set,
memory failure warnings can cause panics and fail fuzz testers that are
stressing memory.

Create a MEM_FAIL() macro to use instead of WARN() in the tracing code
(perhaps this should be a kernel wide macro?), and use that for memory
failure issues. This should stop failing fuzz tests due to warnings.

Link: https://lore.kernel.org/r/CACT4Y+ZP-7np20GVRu3p+eZys9GPtbu+JpfV+HtsufAzvTgJrg@mail.gmail.com
Suggested-by: Dmitry Vyukov <dvyukov@google.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
kernel/trace/ftrace.c
kernel/trace/trace.c
kernel/trace/trace.h