Andrew Morton writes:
> The subtler problem will be interrupt-capable drivers which
> do a bare spin_lock() to serialise wrt their interrupt routines,
> relying upon interrupts being disabled. They'll be deadlocky
> and will need changing. That's trivial to find and fix though.
Uhh, what if you have this situation:
interrupt (level triggered)
enter interrupt handler
printk (can re-enable interrupts?)
enter interrupt handler
printk (can re-enable interrupts?)
enter interrupt handler
printk (can re-enable interrupts?)
....
So surely this isn't a new problem?
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
