From: matt@codeblueprint•co.uk (Matt Fleming)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 3/3] arm64/efi: isolate EFI stub from the kernel proper
Date: Sat, 10 Oct 2015 23:40:09 +0100 [thread overview]
Message-ID: <20151010224009.GJ2723@codeblueprint.co.uk> (raw)
In-Reply-To: <1444330924-17830-4-git-send-email-ard.biesheuvel@linaro.org>
On Thu, 08 Oct, at 08:02:04PM, Ard Biesheuvel wrote:
> Since arm64 does not use a builtin decompressor, the EFI stub is built
> into the kernel proper. So far, this has been working fine, but actually,
> since the stub is in fact a PE/COFF relocatable binary that is executed
> at an unknown offset in the 1:1 mapping provided by the UEFI firmware, we
> should not be seamlessly sharing code with the kernel proper, which is a
> position dependent executable linked at a high virtual offset.
>
> So instead, separate the contents of libstub and its dependencies, by
> putting them into their own namespace by prefixing all of its symbols
> with __efistub. This way, we have tight control over what parts of the
> kernel proper are referenced by the stub.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro•org>
> ---
> arch/arm64/kernel/Makefile | 12 ++++-
> arch/arm64/kernel/efi-entry.S | 10 ++--
> arch/arm64/kernel/head.S | 14 ++---
> arch/arm64/kernel/image.h | 27 ++++++++++
> drivers/firmware/efi/libstub/Makefile | 39 +++++++++++---
> drivers/firmware/efi/libstub/string.c | 57 ++++++++++++++++++++
> 6 files changed, 139 insertions(+), 20 deletions(-)
Reviewed-by: Matt Fleming <matt.fleming@intel•com>
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-10-10 22:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 19:02 [PATCH v4 0/3] arm64: EFI stub isolation Ard Biesheuvel
2015-10-08 19:02 ` [PATCH v4 1/3] arm64/efi: remove /chosen/linux, uefi-stub-kern-ver DT property Ard Biesheuvel
2015-10-10 22:31 ` [PATCH v4 1/3] arm64/efi: remove /chosen/linux,uefi-stub-kern-ver " Matt Fleming
2015-10-08 19:02 ` [PATCH v4 2/3] arm64: use ENDPIPROC() to annotate position independent assembler routines Ard Biesheuvel
2015-10-08 19:02 ` [PATCH v4 3/3] arm64/efi: isolate EFI stub from the kernel proper Ard Biesheuvel
2015-10-09 8:12 ` Andrey Ryabinin
2015-10-09 9:10 ` Will Deacon
2015-10-09 9:40 ` Andrey Ryabinin
2015-10-09 9:43 ` Will Deacon
2015-10-09 9:48 ` Andrey Ryabinin
2015-10-10 22:40 ` Matt Fleming [this message]
2015-10-26 22:26 ` Jeremy Linton
2015-10-26 22:33 ` Jeremy Linton
2015-10-27 2:20 ` Ard Biesheuvel
2015-10-27 14:44 ` Jeremy Linton
2015-10-30 12:17 ` Ard Biesheuvel
2015-10-30 14:35 ` Mark Rutland
2015-10-30 16:01 ` Catalin Marinas
2015-11-02 12:49 ` Matt Fleming
2015-11-24 9:34 ` Robert Richter
2015-11-24 9:38 ` Ard Biesheuvel
2015-10-10 22:40 ` [PATCH v4 0/3] arm64: EFI stub isolation Matt Fleming
2015-10-12 15:30 ` Catalin Marinas
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=20151010224009.GJ2723@codeblueprint.co.uk \
--to=matt@codeblueprint$(echo .)co.uk \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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