summaryrefslogtreecommitdiffstats
path: root/Kconfig
diff options
context:
space:
mode:
authorDoug Berger <opendmb@gmail.com>2017-06-29 18:41:36 +0100
committerRussell King <rmk+kernel@armlinux.org.uk>2017-06-29 23:10:12 +0100
commit9e25ebfe56ece7541cd10a20d715cbdd148a2e06 (patch)
treec16253ba6097189912ebe1924d58367b9e4a77c2 /Kconfig
parentd360a687d99577110c181e67ebfb9a1b6fed63a2 (diff)
downloadtalos-obmc-linux-9e25ebfe56ece7541cd10a20d715cbdd148a2e06.tar.gz
talos-obmc-linux-9e25ebfe56ece7541cd10a20d715cbdd148a2e06.zip
ARM: 8685/1: ensure memblock-limit is pmd-aligned
The pmd containing memblock_limit is cleared by prepare_page_table() which creates the opportunity for early_alloc() to allocate unmapped memory if memblock_limit is not pmd aligned causing a boot-time hang. Commit 965278dcb8ab ("ARM: 8356/1: mm: handle non-pmd-aligned end of RAM") attempted to resolve this problem, but there is a path through the adjust_lowmem_bounds() routine where if all memory regions start and end on pmd-aligned addresses the memblock_limit will be set to arm_lowmem_limit. Since arm_lowmem_limit can be affected by the vmalloc early parameter, the value of arm_lowmem_limit may not be pmd-aligned. This commit corrects this oversight such that memblock_limit is always rounded down to pmd-alignment. Fixes: 965278dcb8ab ("ARM: 8356/1: mm: handle non-pmd-aligned end of RAM") Signed-off-by: Doug Berger <opendmb@gmail.com> Suggested-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud