https://github.com/torvalds/linux
Revision 09cf92b784fae6109450c5d64f9908066d605249 authored by Thomas Gleixner on 05 July 2015, 17:12:35 UTC, committed by Thomas Gleixner on 07 July 2015, 09:54:04 UTC
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
1 parent cbb24dc
History
Tip revision: 09cf92b784fae6109450c5d64f9908066d605249 authored by Thomas Gleixner on 05 July 2015, 17:12:35 UTC
x86/irq: Retrieve irq data after locking irq_desc
Tip revision: 09cf92b

README.AddingFirmware

back to top