linux-kernel - Re: [PATCH] of: alloc anywhere from memblock if range not specified

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:	Thu, 3 Mar 2016 16:52:40 -0600
From:	Rob Herring <robh@...nel.org>
To:	Vinayak Menon <vinmenon@...eaurora.org>
Cc:	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, frowand.list@...il.com,
	grant.likely@...aro.org, m.szyprowski@...sung.com,
	vinayakm.list@...il.com
Subject: Re: [PATCH] of: alloc anywhere from memblock if range not specified

On Mon, Feb 22, 2016 at 07:15:44PM +0530, Vinayak Menon wrote:
> early_init_dt_alloc_reserved_memory_arch passes end as 0 to
> __memblock_alloc_base, when limits are not specified. But
> __memblock_alloc_base takes end value of 0 as MEMBLOCK_ALLOC_ACCESSIBLE
> and limits the end to memblock.current_limit. This results in regions
> never being placed in HIGHMEM area, for e.g. CMA.
> Let __memblock_alloc_base allocate from anywhere in memory if limits are
> not specified.
> 
> Acked-by: Marek Szyprowski <m.szyprowski@...sung.com>
> Signed-off-by: Vinayak Menon <vinmenon@...eaurora.org>

Applied and marked for stable.

Rob