On Tue, 2006-06-06 at 16:59 +0200, Ingo Molnar wrote:
> *
>
> ouch. Then this problem is more urgent than i thought. We definitely
> need the disable_irq_handler(irq, handler) infrastructure and it should
> be used in the most common drivers affected (vortex/3c59x, forcedeth and
> IDE basically).
>
Ingo, did you take a look at my alternative? It postpones the unmasking
of the interrupt till the enable_irq is done. It also doesn't have the
need to update 300+ calls to disable/enable_irq.
Also, the disable_irq_handler doesn't solve the case if the misrouted
irq came from the device that its driver called the disable_irq_handler.
This doesn't affect irqpoll, but for those cases that have broken irq
setups needing irqfixup this can still allow an irq storm.
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
