tracing: Remove RCU work arounds from stack tracer
authorSteven Rostedt (VMware) <rostedt@goodmis.org>
Thu, 21 Sep 2017 17:00:21 +0000 (13:00 -0400)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Sat, 23 Sep 2017 20:50:20 +0000 (16:50 -0400)
commit15516c89acce948debc4c598e03c3fee53045797
tree996cec0ae5b0c7dc3c3c98829308abec41fb3ae0
parente8cac8b1d10589be45671a5ade0926a639b543b7
tracing: Remove RCU work arounds from stack tracer

Currently the stack tracer calls rcu_irq_enter() to make sure RCU
is watching when it records a stack trace. But if the stack tracer
is triggered while tracing inside of a rcu_irq_enter(), calling
rcu_irq_enter() unconditionally can be problematic.

The reason for having rcu_irq_enter() in the first place has been
fixed from within the saving of the stack trace code, and there's no
reason for doing it in the stack tracer itself. Just remove it.

Cc: stable@vger.kernel.org
Fixes: 0be964be0 ("module: Sanitize RCU usage and locking")
Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Suggested-by: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
kernel/trace/trace_stack.c