diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2019-10-17 13:19:01 +0300 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2019-10-24 13:09:21 +0300 |
commit | df4393424af3fbdcd5c404077176082a8ce459c4 (patch) | |
tree | 428c54731cb8408800013c54e75f3ae663b62f27 /arch/x86/kernel/x86_init.c | |
parent | 3b7c59a1950c75f2c0152e5a9cd77675b09233d6 (diff) | |
download | linux-df4393424af3fbdcd5c404077176082a8ce459c4.tar.xz |
x86/ioapic: Prevent inconsistent state when moving an interrupt
There is an issue with threaded interrupts which are marked ONESHOT
and using the fasteoi handler:
if (IS_ONESHOT())
mask_irq();
....
cond_unmask_eoi_irq()
chip->irq_eoi();
if (setaffinity_pending) {
mask_ioapic();
...
move_affinity();
unmask_ioapic();
}
So if setaffinity is pending the interrupt will be moved and then
unconditionally unmasked at the ioapic level, which is wrong in two
aspects:
1) It should be kept masked up to the point where the threaded handler
finished.
2) The physical chip state and the software masked state are inconsistent
Guard both the mask and the unmask with a check for the software masked
state. If the line is marked masked then the ioapic line is also masked, so
both mask_ioapic() and unmask_ioapic() can be skipped safely.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sebastian Siewior <bigeasy@linutronix.de>
Fixes: 3aa551c9b4c4 ("genirq: add threaded interrupt handler support")
Link: https://lkml.kernel.org/r/20191017101938.321393687@linutronix.de
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'arch/x86/kernel/x86_init.c')
0 files changed, 0 insertions, 0 deletions