diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2015-07-05 17:12:35 (GMT) |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2015-07-07 09:54:04 (GMT) |
commit | 09cf92b784fae6109450c5d64f9908066d605249 (patch) | |
tree | 5c4dcac5d736a39342f24a4d7d627a2290f54fb1 /arch/x86/Kconfig | |
parent | cbb24dc761d95fe39a7a122bb1b298e9604cae15 (diff) | |
download | linux-09cf92b784fae6109450c5d64f9908066d605249.tar.xz |
x86/irq: Retrieve irq data after locking irq_desc
irq_data is protected by irq_desc->lock, so retrieving the irq chip
from irq_data outside the lock is racy vs. an concurrent update. Move
it into the lock held region.
While at it add a comment why the vector walk does not require
vector_lock.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: xiao jin <jin.xiao@intel.com>
Cc: Joerg Roedel <jroedel@suse.de>
Cc: Borislav Petkov <bp@suse.de>
Cc: Yanmin Zhang <yanmin_zhang@linux.intel.com>
Link: http://lkml.kernel.org/r/20150705171102.331320612@linutronix.de
Diffstat (limited to 'arch/x86/Kconfig')
0 files changed, 0 insertions, 0 deletions