Re: [PATCH] Prevent nested interrupts when the IRQ stack is near overflowing v2

[Eric W. Biederman]

Andi Kleen <andi@xxxxxxxxxxxxxx> writes:

>> I think the patch as posted solves a real problem, but also perpetuates a bad 
>> situation.
>> 
>> At minimum we should print a (one-time) warning that some badness occured. 
>> That would push us either in the direction of improving drivers, or towards 
>> improving the generic code.
>
> What should a driver do to prevent that? I don't see what it could do
> short of castrating itself (like refusing to use multiple ports)
> As Linus says the driver doesn't know if setting IRQF_DISABLED is safe.

As an aside this is happening on MSI irqs.  They can never be shared.
So in fact the driver can know it is safe.

Should we perhaps make all MSI irqs automatically set IRQF_DISABLED?

Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/