From: opendmb@gmail.com (Doug Berger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ensure memblock-limit is pmd-aligned
Date: Thu, 29 Jun 2017 10:56:56 -0700 [thread overview]
Message-ID: <c261c49e-fb32-7dd7-59e6-2cf29fda6501@gmail.com> (raw)
In-Reply-To: <20170629111645.GC11040@leverpostej>
On 06/29/2017 04:16 AM, Mark Rutland wrote:
> On Tue, Jun 27, 2017 at 10:33:29AM -0700, Doug Berger wrote:
>> 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>
>
> As a minor nit, it would be better for the title to be something like
> "ARM: ensure memblock-limit is pmd-aligned", but either way:
>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
>
> Assuming Russell doesn't have any furhter comments, this looks good to
> drop into the patch system. See:
>
> http://www.arm.linux.org.uk/developer/patches/info.php
>
> ... for instructions on how to send patches there.
>
> Thanks,
> Mark.
>
I modified the title as suggested and it has been submitted as 8685/1.
Thanks!
>> ---
>> Changes for v2:
>> - Cleaner equivalent implementation suggested by Mark Rutland
>> - Revised description to better capture the history
>>
>> arch/arm/mm/mmu.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c
>> index 31af3cb59a60..e46a6a446cdd 100644
>> --- a/arch/arm/mm/mmu.c
>> +++ b/arch/arm/mm/mmu.c
>> @@ -1218,15 +1218,15 @@ void __init adjust_lowmem_bounds(void)
>>
>> high_memory = __va(arm_lowmem_limit - 1) + 1;
>>
>> + if (!memblock_limit)
>> + memblock_limit = arm_lowmem_limit;
>> +
>> /*
>> * Round the memblock limit down to a pmd size. This
>> * helps to ensure that we will allocate memory from the
>> * last full pmd, which should be mapped.
>> */
>> - if (memblock_limit)
>> - memblock_limit = round_down(memblock_limit, PMD_SIZE);
>> - if (!memblock_limit)
>> - memblock_limit = arm_lowmem_limit;
>> + memblock_limit = round_down(memblock_limit, PMD_SIZE);
>>
>> if (!IS_ENABLED(CONFIG_HIGHMEM) || cache_is_vipt_aliasing()) {
>> if (memblock_end_of_DRAM() > arm_lowmem_limit) {
>> --
>> 2.13.0
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2017-06-29 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 17:33 [PATCH v2] ARM: memblock limit must be pmd-aligned Doug Berger
2017-06-29 11:16 ` Mark Rutland
2017-06-29 17:56 ` Doug Berger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c261c49e-fb32-7dd7-59e6-2cf29fda6501@gmail.com \
--to=opendmb@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).