-
Steven Rostedt (VMware) authored
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: 0be964be ("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>
15516c89