linux-kernel - Re: [PATCH] xen: fix the check of e_pfn in xen_find_pfn

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 2 Sep 2015 13:04:26 +0200
From:	Juergen Gross <jgross@...e.com>
To:	zhenzhong.duan@...cle.com, LKML <linux-kernel@...r.kernel.org>
Cc:	david.vrabel@...rix.com, konrad.wilk@...cle.com,
	boris.ostrovsky@...cle.com
Subject: Re: [PATCH] xen: fix the check of e_pfn in xen_find_pfn_range

On 09/02/2015 12:51 PM, Zhenzhong Duan wrote:
> On some numa system, after dom0 up, we see below warning even if there are
> enough pfn ranges could be used for remapping.
> "Unable to find available pfn range, not remapping identity pages"
>
> Fix it to avoid getting a memory region of zero size in xen_find_pfn_range.
>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@...cle.com>

Reviewed-by: Juergen Gross <jgross@...e.com>

> ---
>   arch/x86/xen/setup.c |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
> index a3a7546..c11f6b2 100644
> --- a/arch/x86/xen/setup.c
> +++ b/arch/x86/xen/setup.c
> @@ -178,7 +178,7 @@ static unsigned long __init xen_find_pfn_range(
>           e_pfn = PFN_DOWN(entry->addr + entry->size);
>
>           /* We only care about E820 after this */
> -        if (e_pfn < *min_pfn)
> +        if (e_pfn <= *min_pfn)
>               continue;
>
>           s_pfn = PFN_UP(entry->addr);

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/