From: dennis.chen@arm.com (Dennis Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64:mm Remove the redundant initrd memblock codes
Date: Tue, 5 Jul 2016 10:22:18 +0800 [thread overview]
Message-ID: <20160705022217.GA27637@arm.com> (raw)
In-Reply-To: <4ABE8B9C-8027-40AA-A303-A82CF014A287@linaro.org>
On Mon, Jul 04, 2016 at 12:33:05PM +0200, Ard Biesheuvel wrote:
>
> > On 4 jul. 2016, at 06:53, Dennis Chen <dennis.chen@arm.com> wrote:
> >
> > The memory range between initrd_start and initrd_end was added to the memblock
> > twice unnecessarily in the same function before initrd memory range can be freed.
> > This patch merge those codes into one piece of block and add the initrd memory
> > range only once, also it makes the code clean and simple.
> >
>
> This is likely to break under KASLR (and I would recommend that you test with kaslr enabled when you propose changes to this code)
>
Hello Ard, I've tested it under KASLR on Juno board before proposing the changes,where the firmware provides the RNG protocol, it works well.
>
> The randomization of memstart_addr needs to execute /after/ adding back the initrd, otherwise the chosen value of memstart_addr may push the initrd beyond the end of the linear area into the userland range.
>
Yes, I know the 'range' is depends on memblock_end_of_DRAM() and memblock_start_of_DRAM(), but I can't see that the order of initrd added to the memblock will affect
those two values returned from memblock_ fucntions, IMHO the initrd will be loaded to somewhere within the DRAM by firmware, is that correct?
Thanks,
Dennis
>
>
> > Signed-off-by: Dennis Chen <dennis.chen@arm.com>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Cc: Steve Capper <steve.capper@arm.com>
> > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > Cc: Will Deacon <will.deacon@arm.com>
> > ---
> > arch/arm64/mm/init.c | 58 +++++++++++++++++++++++-----------------------------
> > 1 file changed, 26 insertions(+), 32 deletions(-)
> >
> > diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> > index 2ade7a6..cf26cdb 100644
> > --- a/arch/arm64/mm/init.c
> > +++ b/arch/arm64/mm/init.c
> > @@ -228,6 +228,29 @@ void __init arm64_memblock_init(void)
> > memblock_add(__pa(_text), (u64)(_end - _text));
> > }
> >
> > + if (IS_ENABLED(CONFIG_RANDOMIZE_BASE)) {
> > + extern u16 memstart_offset_seed;
> > + u64 range = linear_region_size -
> > + (memblock_end_of_DRAM() - memblock_start_of_DRAM());
> > +
> > + /*
> > + * If the size of the linear region exceeds, by a sufficient
> > + * margin, the size of the region that the available physical
> > + * memory spans, randomize the linear region as well.
> > + */
> > + if (memstart_offset_seed > 0 && range >= ARM64_MEMSTART_ALIGN) {
> > + range = range / ARM64_MEMSTART_ALIGN + 1;
> > + memstart_addr -= ARM64_MEMSTART_ALIGN *
> > + ((range * memstart_offset_seed) >> 16);
> > + }
> > + }
> > +
> > + /*
> > + * Register the kernel text, kernel data, initrd, and initial
> > + * pagetables with memblock.
> > + */
> > + memblock_reserve(__pa(_text), _end - _text);
> > +
> > if (IS_ENABLED(CONFIG_BLK_DEV_INITRD) && initrd_start) {
> > /*
> > * Add back the memory we just removed if it results in the
> > @@ -254,41 +277,12 @@ void __init arm64_memblock_init(void)
> > memblock_remove(base, size); /* clear MEMBLOCK_ flags */
> > memblock_add(base, size);
> > memblock_reserve(base, size);
> > + /* the generic initrd code expects virtual addresses */
> > + initrd_start = __phys_to_virt(initrd_start);
> > + initrd_end = __phys_to_virt(initrd_end);
> > }
> > }
> >
> > - if (IS_ENABLED(CONFIG_RANDOMIZE_BASE)) {
> > - extern u16 memstart_offset_seed;
> > - u64 range = linear_region_size -
> > - (memblock_end_of_DRAM() - memblock_start_of_DRAM());
> > -
> > - /*
> > - * If the size of the linear region exceeds, by a sufficient
> > - * margin, the size of the region that the available physical
> > - * memory spans, randomize the linear region as well.
> > - */
> > - if (memstart_offset_seed > 0 && range >= ARM64_MEMSTART_ALIGN) {
> > - range = range / ARM64_MEMSTART_ALIGN + 1;
> > - memstart_addr -= ARM64_MEMSTART_ALIGN *
> > - ((range * memstart_offset_seed) >> 16);
> > - }
> > - }
> > -
> > - /*
> > - * Register the kernel text, kernel data, initrd, and initial
> > - * pagetables with memblock.
> > - */
> > - memblock_reserve(__pa(_text), _end - _text);
> > -#ifdef CONFIG_BLK_DEV_INITRD
> > - if (initrd_start) {
> > - memblock_reserve(initrd_start, initrd_end - initrd_start);
> > -
> > - /* the generic initrd code expects virtual addresses */
> > - initrd_start = __phys_to_virt(initrd_start);
> > - initrd_end = __phys_to_virt(initrd_end);
> > - }
> > -#endif
> > -
> > early_init_fdt_scan_reserved_mem();
> >
> > /* 4GB maximum for 32-bit only capable devices */
> > --
> > 1.8.3.1
> >
>
next prev parent reply other threads:[~2016-07-05 2:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 4:53 [PATCH] arm64:mm Remove the redundant initrd memblock codes Dennis Chen
2016-07-04 10:33 ` Ard Biesheuvel
2016-07-05 2:22 ` Dennis Chen [this message]
2016-07-05 3:41 ` Ard Biesheuvel
2016-07-05 4:18 ` Dennis Chen
2016-07-06 8:47 ` Ard Biesheuvel
2016-07-06 10:07 ` Dennis Chen
2016-07-06 14:41 ` Ard Biesheuvel
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=20160705022217.GA27637@arm.com \
--to=dennis.chen@arm.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).