irq: Ensure irq_exit() code runs with interrupts disabled
authorThomas Gleixner <tglx@linutronix.de>
Wed, 20 Feb 2013 21:00:48 +0000 (22:00 +0100)
committerThomas Gleixner <tglx@linutronix.de>
Thu, 21 Feb 2013 19:52:24 +0000 (20:52 +0100)
commit74eed0163d0def3fce27228d9ccf3d36e207b286
tree28aa386f02468504846ebec731e9ba432e4a4010
parente5ab012c3271990e8457055c25cafddc1ae8aa6b
irq: Ensure irq_exit() code runs with interrupts disabled

We had already a few problems with code called from irq_exit() when
interrupted from a nesting interrupt. This can happen on architectures
which do not define __ARCH_IRQ_EXIT_IRQS_DISABLED.

__ARCH_IRQ_EXIT_IRQS_DISABLED should go away and we want to make it
mandatory to call irq_exit() with interrupts disabled.

As a temporary protection disable interrupts for those architectures
which do not define __ARCH_IRQ_EXIT_IRQS_DISABLED and add a WARN_ONCE
when an architecture which defines __ARCH_IRQ_EXIT_IRQS_DISABLED calls
irq_exit() with interrupts enabled.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Linus Torvalds <torvalds@linuxfoundation.org>
Link: http://lkml.kernel.org/r/alpine.LFD.2.02.1302202155320.22263@ionos
kernel/softirq.c