From: Ard Biesheuvel <ardb@kernel.org>
To: linux-efi@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
broonie@kernel.org, will@kernel.org, catalin.marinas@arm.com,
Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH v2 0/6] arm64/efi/zboot: Clean up and enable BTI annotation
Date: Tue, 18 Apr 2023 15:49:46 +0200 [thread overview]
Message-ID: <20230418134952.1170141-1-ardb@kernel.org> (raw)
Some tweaks for the arm64 EFI header and the zboot version, to add the
annotation that informs the loader that the code regions may be mapped
with BTI enforcement enabled.
As a related cleanup, add the combined codesize (text+rodata+inittext)
to the arm64 Image header, so the EFI zboot loader can grab it from the
image after decompressing it.
Changes since v1:
- instead of adding a proper header field, only pass the code size via
the image header when generating the zboot image, using the
text_offset field which still has meaning in the bare metal ABI (which
means bare metal loaders must honour it) but is actually no longer in
use.
Ard Biesheuvel (6):
efi/pe: Import new BTI/IBT header flags from the spec
arm64: efi: Enable BTI codegen and add PE/COFF annotation
efi/zboot: arm64: Poke kernel code size into the zboot payload image
header
efi/zboot: Add BSS padding before compression
efi/zboot: Set forward edge CFI compat header flag if supported
efi/zboot: arm64: Grab code size from image header
arch/arm64/boot/Makefile | 24 ++++++-
arch/arm64/kernel/efi-header.S | 71 ++++++++++++--------
arch/arm64/kernel/image-vars.h | 4 ++
drivers/firmware/efi/libstub/Makefile | 3 +-
drivers/firmware/efi/libstub/Makefile.zboot | 41 +++++++----
drivers/firmware/efi/libstub/arm64.c | 26 +++++--
drivers/firmware/efi/libstub/efistub.h | 3 +-
drivers/firmware/efi/libstub/zboot-header.S | 51 +++++++++-----
drivers/firmware/efi/libstub/zboot.c | 13 +---
include/linux/pe.h | 4 ++
10 files changed, 160 insertions(+), 80 deletions(-)
--
2.39.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-04-18 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 13:49 Ard Biesheuvel [this message]
2023-04-18 13:49 ` [PATCH v2 1/6] efi/pe: Import new BTI/IBT header flags from the spec Ard Biesheuvel
2023-04-18 13:49 ` [PATCH v2 2/6] arm64: efi: Enable BTI codegen and add PE/COFF annotation Ard Biesheuvel
2023-04-18 13:49 ` [PATCH v2 3/6] efi/zboot: arm64: Poke kernel code size into the zboot payload image header Ard Biesheuvel
2023-04-18 13:49 ` [PATCH v2 4/6] efi/zboot: Add BSS padding before compression Ard Biesheuvel
2023-04-18 13:49 ` [PATCH v2 5/6] efi/zboot: Set forward edge CFI compat header flag if supported Ard Biesheuvel
2023-04-18 13:49 ` [PATCH v2 6/6] efi/zboot: arm64: Grab code size from image header 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=20230418134952.1170141-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.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).