David Vrabel 0b80fa4b24 xen/events: don't bind non-percpu VIRQs with percpu chip ... commit 77bb3dfdc0d554befad58fdefbc41be5bc3ed38a upstream. 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> [lizf: Backported to 3.4: adjust filename] Signed-off-by: Zefan Li <lizefan@huawei.com>		2015-09-18 09:20:42 +08:00
..
interface	xen-netfront: reduce gso_max_size to account for max TCP header	2014-06-07 16:02:15 -07:00
balloon.h
events.h	xen/events: don't bind non-percpu VIRQs with percpu chip	2015-09-18 09:20:42 +08:00
evtchn.h
features.h
gntalloc.h
gntdev.h
grant_table.h
hvc-console.h
hvm.h
Kbuild
page.h
platform_pci.h
privcmd.h
swiotlb-xen.h
tmem.h
xen-ops.h
xen.h
xenbus.h
xenbus_dev.h
xencomm.h