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

> 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 doshort of castrating itself (like refusing to use multiple ports)As Linus says the driver doesn't know if setting IRQF_DISABLED is safe.