xen/events: avoid NULL pointer dereference in dom0 on large machines
authorJuergen Gross <jgross@suse.com>
Thu, 26 Feb 2015 05:52:05 +0000 (06:52 +0100)
committerSasha Levin <sasha.levin@oracle.com>
Sat, 28 Mar 2015 13:59:51 +0000 (09:59 -0400)
commit72c7a8558c74d6162126547f1a89e54d94dcd86f
tree34f32b7bd6b99495b5f0db5badfaf4ae89e00ecb
parent75391143ec736e21f6a77c1aa9b96cc67a98898f
xen/events: avoid NULL pointer dereference in dom0 on large machines

[ Upstream commit 85e40b0539b24518c8bdf63e2605c8522377d00f ]

Using the pvops kernel a NULL pointer dereference was detected on a
large machine (144 processors) when booting as dom0 in
evtchn_fifo_unmask() during assignment of a pirq.

The event channel in question was the first to need a new entry in
event_array[] in events_fifo.c. Unfortunately xen_irq_info_pirq_setup()
is called with evtchn being 0 for a new pirq and the real event channel
number is assigned to the pirq only during __startup_pirq().

It is mandatory to call xen_evtchn_port_setup() after assigning the
event channel number to the pirq to make sure all memory needed for the
event channel is allocated.

Signed-off-by: Juergen Gross <jgross@suse.com>
Cc: <stable@vger.kernel.org> # 3.14+
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
drivers/xen/events/events_base.c