On Sat, Apr 17, 2010 at 02:29:06PM -0700, David Miller wrote: > From: Frederic Weisbecker <fweisbec@xxxxxxxxx> > Date: Sat, 17 Apr 2010 19:22:21 +0200 > > > I tested the following patch and it fixes the issue after several > > manual loops of: > > Wait, this is completely normal. > > NMIs can come in at any time and nmi_enter() emits a trace via the > rcu_nmi_enter(). > > This happens on x86 too. Yeah but I've dumped the recursion cases I could find and there was no NMI path. I haven't started the watchdog nor perf, I guess NMI don't trigger in other cases, right? For now, the only reentrancy I could find was irqs that interrupt the tracing path. Which means no good clue there. That said I have only logged recursivity on trace entry path, not yet on return. I'm disabling the protections on entry, just to narrow down the recursivity place, in case it only happens on return. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
