From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: kaslr: Adjust the offset to avoid Image across alignment boundary
Date: Fri, 18 Aug 2017 16:19:21 +0100 [thread overview]
Message-ID: <20170818151920.jpugpcgwiavgwgaf@armageddon.cambridge.arm.com> (raw)
In-Reply-To: <20170818150435.35224-1-catalin.marinas@arm.com>
On Fri, Aug 18, 2017 at 04:04:34PM +0100, Catalin Marinas wrote:
> With 16KB pages and a kernel Image larger than 16MB, the current
> kaslr_early_init() logic for avoiding mappings across swapper table
> boundaries fails since increasing the offset by kimg_sz just moves the
> problem to the next boundary.
>
> This patch decreases the offset by the boundary overflow amount, with
> slight risk of reduced entropy as the kernel is more likely to be found
> at kimg_sz below a swapper table boundary.
>
> Trying-to-fix: afd0e5a87670 ("arm64: kaslr: Fix up the kernel image alignment")
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Neeraj Upadhyay <neeraju@codeaurora.org>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> ---
>
> While preparing this email, I noticed that the kernel eventually failed
> to boot, though after a lot more reboot iterations. Mark Rutland also
> managed to make the KASLR kernel fail to boot with 64K pages which
> wouldn't be explained by this patch.
>
> So, any suggestions are welcome. My testing method, qemu starting a
> guest in a loop with virtio-rng-pci.
Apparently, the booting gets much more stable if I disable the physical
relocation in arm64-stub.c (but keep the virtual one with the fix in
this patch). So I guess we are chasing two different issues.
--
Catalin
next prev parent reply other threads:[~2017-08-18 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 15:04 [PATCH] arm64: kaslr: Adjust the offset to avoid Image across alignment boundary Catalin Marinas
2017-08-18 15:19 ` Catalin Marinas [this message]
2017-08-18 15:20 ` Ard Biesheuvel
2017-08-18 15:22 ` Catalin Marinas
2017-08-18 15:24 ` Ard Biesheuvel
2017-08-18 15:29 ` Ard Biesheuvel
2017-08-18 15:33 ` Catalin Marinas
2017-08-18 15:35 ` Mark Rutland
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=20170818151920.jpugpcgwiavgwgaf@armageddon.cambridge.arm.com \
--to=catalin.marinas@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