diff options
| author | Jan Beulich <JBeulich@suse.com> | 2016-05-04 07:02:36 -0600 |
|---|---|---|
| committer | David Vrabel <david.vrabel@citrix.com> | 2016-05-04 16:37:01 +0100 |
| commit | 27e0e6385377c4dc68a4ddaf1a35a2dfa951f3c5 (patch) | |
| tree | 940f070cecbb3f335be0c1f976a472c990ebf4ab | |
| parent | dfd74a1edfaba5864276a2859190a8d242d18952 (diff) | |
xen/evtchn: fix ring resize when binding new events
The copying of ring data was wrong for two cases: For a full ring
nothing got copied at all (as in that case the canonicalized producer
and consumer indexes are identical). And in case one or both of the
canonicalized (after the resize) indexes would point into the second
half of the buffer, the copied data ended up in the wrong (free) part
of the new buffer. In both cases uninitialized data would get passed
back to the caller.
Fix this by simply copying the old ring contents twice: Once to the
low half of the new buffer, and a second time to the high half.
This addresses the inability to boot a HVM guest with 64 or more
vCPUs. This regression was caused by 8620015499101090 (xen/evtchn:
dynamically grow pending event channel ring).
Reported-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Cc: <stable@vger.kernel.org> # 4.4+
Signed-off-by: David Vrabel <david.vrabel@citrix.com>