Ingo Molnar wrote:
which precise locking situation do you mean?
cpu 1: acquire random networking spin_lock_bh()
cpu 2: read_lock(&tasklist_lock) from process context interrupt. softirq. within softirq: try to acquire the networking lock. * spins.
cpu 1: hardware interrupt within hw interrupt: signal delivery. tries to acquire tasklist_lock.
--> deadlock.
-- Manfred - 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/
