summaryrefslogtreecommitdiffstats
path: root/include/linux/memblock.h
diff options
context:
space:
mode:
authorDimitri Sivanich <sivanich@sgi.com>2012-10-16 07:50:21 -0500
committerIngo Molnar <mingo@kernel.org>2012-10-24 12:53:51 +0200
commit94777fc51b3ad85ff9f705ddf7cdd0eb3bbad5a6 (patch)
treea30f45b8fe826841522cba4fc0b4c45fe3c54778 /include/linux/memblock.h
parent3e8fa263a97079c74880675c451587bb6899e661 (diff)
downloadlinux-94777fc51b3ad85ff9f705ddf7cdd0eb3bbad5a6.tar.gz
linux-94777fc51b3ad85ff9f705ddf7cdd0eb3bbad5a6.tar.bz2
linux-94777fc51b3ad85ff9f705ddf7cdd0eb3bbad5a6.zip
x86/irq/ioapic: Check for valid irq_cfg pointer in smp_irq_move_cleanup_interrupt
Posting this patch to fix an issue concerning sparse irq's that I raised a while back. There was discussion about adding refcounting to sparse irqs (to fix other potential race conditions), but that does not appear to have been addressed yet. This covers the only issue of this type that I've encountered in this area. A NULL pointer dereference can occur in smp_irq_move_cleanup_interrupt() if we haven't yet setup the irq_cfg pointer in the irq_desc.irq_data.chip_data. In create_irq_nr() there is a window where we have set vector_irq in __assign_irq_vector(), but not yet called irq_set_chip_data() to set the irq_cfg pointer. Should an IRQ_MOVE_CLEANUP_VECTOR hit the cpu in question during this time, smp_irq_move_cleanup_interrupt() will attempt to process the aforementioned irq, but panic when accessing irq_cfg. Only continue processing the irq if irq_cfg is non-NULL. Signed-off-by: Dimitri Sivanich <sivanich@sgi.com> Cc: Suresh Siddha <suresh.b.siddha@intel.com> Cc: Joerg Roedel <joerg.roedel@amd.com> Cc: Yinghai Lu <yinghai@kernel.org> Cc: Alexander Gordeev <agordeev@redhat.com> Link: http://lkml.kernel.org/r/20121016125021.GA22935@sgi.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'include/linux/memblock.h')
0 files changed, 0 insertions, 0 deletions