arm64: account for sparsemem section alignment when choosing vmemmap offset
authorArd Biesheuvel <ard.biesheuvel@linaro.org>
Tue, 8 Mar 2016 14:09:29 +0000 (21:09 +0700)
committerSasha Levin <sasha.levin@oracle.com>
Wed, 13 Apr 2016 21:14:28 +0000 (17:14 -0400)
commitfc7260739ac5739520454788f2e8e667f92f1a29
treeda8e7c16b0cf62082d6f1eed87edfcc2bbd40552
parent6d7ac2feca9c07d9ce489dbaab2f51beb3e5c107
arm64: account for sparsemem section alignment when choosing vmemmap offset

[ Upstream commit 36e5cd6b897e17d03008f81e075625d8e43e52d0 ]

Commit dfd55ad85e4a ("arm64: vmemmap: use virtual projection of linear
region") fixed an issue where the struct page array would overflow into the
adjacent virtual memory region if system RAM was placed so high up in
physical memory that its addresses were not representable in the build time
configured virtual address size.

However, the fix failed to take into account that the vmemmap region needs
to be relatively aligned with respect to the sparsemem section size, so that
a sequence of page structs corresponding with a sparsemem section in the
linear region appears naturally aligned in the vmemmap region.

So round up vmemmap to sparsemem section size. Since this essentially moves
the projection of the linear region up in memory, also revert the reduction
of the size of the vmemmap region.

Cc: <stable@vger.kernel.org>
Fixes: dfd55ad85e4a ("arm64: vmemmap: use virtual projection of linear region")
Tested-by: Mark Langsdorf <mlangsdo@redhat.com>
Tested-by: David Daney <david.daney@cavium.com>
Tested-by: Robert Richter <rrichter@cavium.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
arch/arm64/include/asm/pgtable.h