David Vrabel 77bb3dfdc0 xen/events: don't bind non-percpu VIRQs with percpu chip ... A non-percpu VIRQ (e.g., VIRQ_CONSOLE) may be freed on a different VCPU than it is bound to. This can result in a race between handle_percpu_irq() and removing the action in __free_irq() because handle_percpu_irq() does not take desc->lock. The interrupt handler sees a NULL action and oopses. Only use the percpu chip/handler for per-CPU VIRQs (like VIRQ_TIMER). # cat /proc/interrupts | grep virq 40: 87246 0 xen-percpu-virq timer0 44: 0 0 xen-percpu-virq debug0 47: 0 20995 xen-percpu-virq timer1 51: 0 0 xen-percpu-virq debug1 69: 0 0 xen-dyn-virq xen-pcpu 74: 0 0 xen-dyn-virq mce 75: 29 0 xen-dyn-virq hvc_console Signed-off-by: David Vrabel <david.vrabel@citrix.com> Cc: <stable@vger.kernel.org>		2015-05-19 19:55:36 +01:00
..
interface
acpi.h
balloon.h
events.h	xen/events: don't bind non-percpu VIRQs with percpu chip	2015-05-19 19:55:36 +01:00
features.h
grant_table.h	xen/grant: introduce func gnttab_unmap_refs_sync()	2015-04-27 11:41:12 +01:00
hvc-console.h
hvm.h
page.h
platform_pci.h
swiotlb-xen.h
tmem.h
xen-ops.h	xen: Suspend ticks on all CPUs during suspend	2015-04-29 17:10:05 +01:00
xen.h
xenbus_dev.h
xenbus.h	xenbus_client: Extend interface to support multi-page ring	2015-04-15 10:56:47 +01:00