On Fri, 2 Apr 2010, Pavel Machek wrote: > On Wed 2010-03-31 13:16:37, Thomas Gleixner wrote: > > On Tue, 30 Mar 2010, Andi Kleen wrote: > > > > > > Why not simply force IRQF_DISABLED for all MSI interrupts. That still > > > > allows nesting for non MSI ones, but it limits the chance of throwing > > > > up reasonably well. That's a two liner. > > > > > > > > Can you please test whether it resolves the issue at hand ? > > > > > > Sorry for the late answer. Got confirmation that this patch > > > fixes the test case. Thanks. > > > > Ok, I'll push it linus wards and cc stable. I think thats the least > > intrusive safe bet we can have right now. > > stable? I'd say thats way too intrusive for -stable... So we better let the possible stack overruns unaddressed ? Thanks, tglx -- 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