x86/xen: Do not clip xen_e820_map to xen_e820_map_entries when sanitizing map
authorMalcolm Crossley <malcolm.crossley@citrix.com>
Mon, 28 Sep 2015 10:36:52 +0000 (11:36 +0100)
committerBen Hutchings <ben@decadent.org.uk>
Tue, 17 Nov 2015 15:54:40 +0000 (15:54 +0000)
commita92a5446e2482938e1bce89789235cf814cd85d1
tree24a428f7b8402cf7b43a15b174baefe1452e3317
parentd599a135f9562d30b74fefc3315d9490981cfd3f
x86/xen: Do not clip xen_e820_map to xen_e820_map_entries when sanitizing map

commit 64c98e7f49100b637cd20a6c63508caed6bbba7a upstream.

Sanitizing the e820 map may produce extra E820 entries which would result in
the topmost E820 entries being removed. The removed entries would typically
include the top E820 usable RAM region and thus result in the domain having
signicantly less RAM available to it.

Fix by allowing sanitize_e820_map to use the full size of the allocated E820
array.

Signed-off-by: Malcolm Crossley <malcolm.crossley@citrix.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
[bwh: Backported to 3.2:
 s/xen_e820_map_entries/memmap.nr_entries/; s/xen_e820_map/map/g]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
arch/x86/xen/setup.c