History

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.

Doug Berger committed 9 years ago

Commit 9e25ebf1 parent d360a681 file · +4 −4Browse files

Unified · Split

arch/arm/mm/mmu.c+4−4
@@ -1218,15 +1218,15 @@ void __init adjust_lowmem_bounds(void) · 1217 unmodified lines
12181218
12191219 high_memory = __va(arm_lowmem_limit - 1) + 1;
12201220
1221+ if (!memblock_limit)
1222+ memblock_limit = arm_lowmem_limit;
1223+
12211224 /*
12221225 * Round the memblock limit down to a pmd size. This
12231226 * helps to ensure that we will allocate memory from the
12241227 * last full pmd, which should be mapped.
12251228 */
1226− if (memblock_limit)
1227− memblock_limit = round_down(memblock_limit, PMD_SIZE);
1228− if (!memblock_limit)
1229− memblock_limit = arm_lowmem_limit;
1229+ memblock_limit = round_down(memblock_limit, PMD_SIZE);
12301230
12311231 if (!IS_ENABLED(CONFIG_HIGHMEM) || cache_is_vipt_aliasing()) {
12321232 if (memblock_end_of_DRAM() > arm_lowmem_limit) {

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t