Re: [Xen-devel] [PATCH] x86/xen: Do not clip xen_e820_map to xen_e820_map_entries when sanitizing map

[David Vrabel <david.vrabel@xxxxxxxxxx>]

On 28/09/15 11:36, Malcolm Crossley wrote:
> 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.

Applied to for-linus-4.3b and tagged for stable, thanks.

David
> 
> Signed-off-by: Malcolm Crossley <malcolm.crossley@xxxxxxxxxx>
> ---
>  arch/x86/xen/setup.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
> index f5ef674..415a55f 100644
> --- a/arch/x86/xen/setup.c
> +++ b/arch/x86/xen/setup.c
> @@ -798,7 +798,7 @@ char * __init xen_memory_setup(void)
>               xen_ignore_unusable();
>  
>       /* Make sure the Xen-supplied memory map is well-ordered. */
> -     sanitize_e820_map(xen_e820_map, xen_e820_map_entries,
> +     sanitize_e820_map(xen_e820_map, ARRAY_SIZE(xen_e820_map),
>                         &xen_e820_map_entries);
>  
>       max_pages = xen_get_max_pages();
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel