[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGa+x85rWSAw0KCt-gJTkpvfur5ujYYqQXGJ0G+z135udTHYgw@mail.gmail.com>
Date: Tue, 28 Jan 2014 17:25:19 -0800
From: Kevin Hilman <khilman@...aro.org>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Olof Johansson <olof@...om.net>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Dave Hansen <dave.hansen@...el.com>,
Santosh Shilimkar <santosh.shilimkar@...com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] memblock: Add limit checking to memblock_virt_alloc
On Tue, Jan 28, 2014 at 2:04 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> In original bootmem wrapper for memblock, we have limit checking.
>
> Add it to memblock_virt_alloc, to address arm and x86 booting crash.
>
> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
>
> ---
> mm/memblock.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> Index: linux-2.6/mm/memblock.c
> ===================================================================
> --- linux-2.6.orig/mm/memblock.c
> +++ linux-2.6/mm/memblock.c
> @@ -1077,6 +1077,9 @@ static void * __init memblock_virt_alloc
> if (!align)
> align = SMP_CACHE_BYTES;
>
> + if (max_addr > memblock.current_limit)
> + max_addr = memblock.current_limit;
> +
> again:
> alloc = memblock_find_in_range_node(size, align, min_addr, max_addr,
> nid);
Tested-by: Kevin Hilman <khilman@...aro.org>
Verified various ARM boots to be passing again.
Kevin
--
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/
Powered by blists - more mailing lists