]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
genirq: Prevent chip buslock deadlock
authorThomas Gleixner <tglx@linutronix.de>
Sun, 13 Dec 2015 17:12:30 +0000 (18:12 +0100)
committerJiri Slaby <jslaby@suse.cz>
Thu, 3 Mar 2016 11:45:54 +0000 (12:45 +0100)
commit5df68eedfb0e3cfa8c23c8b0b28bf032881313e4
treeee48ee8349c94cbedf011d13744ab375d1002814
parent281eea0a8603241edc3fe38c1ab4fa0a92ebec2b
genirq: Prevent chip buslock deadlock

commit abc7e40c81d113ef4bacb556f0a77ca63ac81d85 upstream.

If a interrupt chip utilizes chip->buslock then free_irq() can
deadlock in the following way:

CPU0 CPU1
interrupt(X) (Shared or spurious)
free_irq(X) interrupt_thread(X)
chip_bus_lock(X)
   irq_finalize_oneshot(X)
     chip_bus_lock(X)
synchronize_irq(X)

synchronize_irq() waits for the interrupt thread to complete,
i.e. forever.

Solution is simple: Drop chip_bus_lock() before calling
synchronize_irq() as we do with the irq_desc lock. There is nothing to
be protected after the point where irq_desc lock has been released.

This adds chip_bus_lock/unlock() to the remove_irq() code path, but
that's actually correct in the case where remove_irq() is called on
such an interrupt. The current users of remove_irq() are not affected
as none of those interrupts is on a chip which requires buslock.

Reported-by: Fredrik Markström <fredrik.markstrom@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
kernel/irq/manage.c