Revision b00d607bb188e187c7b60074d2fa91a6f1985029 authored by Steven Rostedt (VMware) on 05 December 2017, 09:41:51 UTC, committed by Steven Rostedt (VMware) on 15 December 2017, 01:48:22 UTC
The stack tracer records a stack dump whenever it sees a stack usage that is more than what it ever saw before. This can happen at any function that is being traced. If it happens when the CPU is going idle (or other strange locations), RCU may not be watching, and in this case, the recording of the stack trace will trigger a warning. There's been lots of efforts to make hacks to allow stack tracing to proceed even if RCU is not watching, but this only causes more issues to appear. Simply do not trace a stack if RCU is not watching. It probably isn't a bad stack anyway. Acked-by: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
1 parent a773d41
.cocciconfig
[spatch]
options = --timeout 200
options = --use-gitgrep
Computing file changes ...
