On Wed, 13 Dec 2017 20:34:34 -0800 "Paul E. McKenney" <paul...@linux.vnet.ibm.com> wrote:
> On Wed, Dec 13, 2017 at 03:47:03PM -0500, Steven Rostedt wrote: > > From: "Steven Rostedt (VMware)" <rost...@goodmis.org> > > > > 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. > > > > Cc: "Paul E. McKenney" <paul...@linux.vnet.ibm.com> > > Signed-off-by: Steven Rostedt (VMware) <rost...@goodmis.org> > > Acked-by: "Paul E. McKenney" <paul...@linux.vnet.ibm.com> > Thanks! -- Steve
