From: Steven Rostedt <rostedt@xxxxxxxxxxx>
Date: Tue, 06 Apr 2010 21:13:10 -0400
> On Tue, 2010-04-06 at 15:28 +0200, Peter Zijlstra wrote:
>
>> Index: linux-2.6/kernel/trace/trace_irqsoff.c
>> ===================================================================
>> --- linux-2.6.orig/kernel/trace/trace_irqsoff.c
>> +++ linux-2.6/kernel/trace/trace_irqsoff.c
>> @@ -316,6 +316,14 @@ void trace_hardirqs_off(void)
>> }
>> EXPORT_SYMBOL(trace_hardirqs_off);
>>
>> +void trace_hardirqs_off_no_nmi(void)
>> +{
>> + WARN_ON_ONCE(in_nmi());
>
> Should we do this for all archs? I can imagine a lot of warning reports
> coming in the near future. And they will be passing it towards me.
That's the whole point, so that the problem is more easily noticed and
it gets fixed long before I end up accidently testing the code on my
machines :-)
To be honest, the fix is so trivial, you just need to add '_nmi' to
the local_irq_{save,restore}() calls that warn like this.
I'm even willing to have you forward all of those reports to me and
I'll be responsible for fixing them.
How's that? :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
