From: Ard Biesheuvel <ardb@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-efi@vger.kernel.org, mark.rutland@arm.com,
catalin.marinas@arm.com, will@kernel.org,
Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH 0/2] arm64: Expose kernel code size to EFI zboot code
Date: Wed, 26 Apr 2023 16:11:01 +0200 [thread overview]
Message-ID: <20230426141103.2464423-1-ardb@kernel.org> (raw)
The EFI zboot code needs access to the kernel code size, in order to be
able to determine which part of the image needs to be cleaned to the
PoU, and does not tolerate being mapped with non-executable permissions.
Instead of adding [0] this to the kernel image header, which makes it
ABI, let's use Kbuild rules to inject this quantity into the zboot
payload ELF object.
[0] https://lore.kernel.org/all/20230418134952.1170141-1-ardb@kernel.org/
Ard Biesheuvel (2):
efi/zboot: arm64: Inject kernel code size symbol into the zboot
payload
efi/zboot: arm64: Grab kernel code size from zboot payload
arch/arm64/boot/Makefile | 3 +++
arch/arm64/kernel/image-vars.h | 4 ++++
drivers/firmware/efi/libstub/Makefile.zboot | 16 ++++------------
drivers/firmware/efi/libstub/arm64.c | 19 +++++++++++++------
drivers/firmware/efi/libstub/efistub.h | 3 +--
drivers/firmware/efi/libstub/zboot.c | 15 ++++-----------
drivers/firmware/efi/libstub/zboot.lds | 7 +++++++
7 files changed, 36 insertions(+), 31 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-26 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 14:11 Ard Biesheuvel [this message]
2023-04-26 14:11 ` [PATCH 1/2] efi/zboot: arm64: Inject kernel code size symbol into the zboot payload Ard Biesheuvel
2023-04-26 15:58 ` Mark Rutland
2023-04-26 14:11 ` [PATCH 2/2] efi/zboot: arm64: Grab kernel code size from " Ard Biesheuvel
2023-04-26 14:20 ` Ard Biesheuvel
2023-04-26 15:57 ` 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=20230426141103.2464423-1-ardb@kernel.org \
--to=ardb@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).