linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-efi@vger.kernel.org,
	catalin.marinas@arm.com, will@kernel.org
Subject: Re: [PATCH 1/2] efi/zboot: arm64: Inject kernel code size symbol into the zboot payload
Date: Wed, 26 Apr 2023 16:58:37 +0100	[thread overview]
Message-ID: <ZElKHGu2Xd/mAvoo@FVFF77S0Q05N> (raw)
In-Reply-To: <20230426141103.2464423-2-ardb@kernel.org>

On Wed, Apr 26, 2023 at 04:11:02PM +0200, Ard Biesheuvel wrote:
> The EFI zboot code is not built as part of the kernel proper, like the
> ordinary EFI stub, but still needs access to symbols that are defined
> only internally in the kernel, and are left unexposed deliberately to
> avoid creating ABI inadvertently that we're stuck with later.
> 
> So capture the kernel code size of the kernel image, and inject it as an
> ELF symbol into the object that contains the compressed payload, where
> it will be accessible to zboot code that needs it.
> 
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>

Acked-by: Mark Rutland <mark.rutland@arm.com>

Mark.

> ---
>  arch/arm64/boot/Makefile                    | 3 +++
>  arch/arm64/kernel/image-vars.h              | 4 ++++
>  drivers/firmware/efi/libstub/Makefile.zboot | 2 +-
>  drivers/firmware/efi/libstub/zboot.lds      | 7 +++++++
>  4 files changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/boot/Makefile b/arch/arm64/boot/Makefile
> index ae645fda90bca574..1761f5972443fc50 100644
> --- a/arch/arm64/boot/Makefile
> +++ b/arch/arm64/boot/Makefile
> @@ -44,4 +44,7 @@ EFI_ZBOOT_BFD_TARGET	:= elf64-littleaarch64
>  EFI_ZBOOT_MACH_TYPE	:= ARM64
>  EFI_ZBOOT_FORWARD_CFI	:= $(CONFIG_ARM64_BTI_KERNEL)
>  
> +EFI_ZBOOT_OBJCOPY_FLAGS	= --add-symbol zboot_code_size=0x$(shell \
> +				$(NM) vmlinux|grep _kernel_codesize|cut -d' ' -f1)
> +
>  include $(srctree)/drivers/firmware/efi/libstub/Makefile.zboot
> diff --git a/arch/arm64/kernel/image-vars.h b/arch/arm64/kernel/image-vars.h
> index 8309197c0ebd4a8e..35f3c79595137354 100644
> --- a/arch/arm64/kernel/image-vars.h
> +++ b/arch/arm64/kernel/image-vars.h
> @@ -108,4 +108,8 @@ KVM_NVHE_ALIAS(kvm_protected_mode_initialized);
>  
>  #endif /* CONFIG_KVM */
>  
> +#ifdef CONFIG_EFI_ZBOOT
> +_kernel_codesize = ABSOLUTE(__inittext_end - _text);
> +#endif
> +
>  #endif /* __ARM64_KERNEL_IMAGE_VARS_H */
> diff --git a/drivers/firmware/efi/libstub/Makefile.zboot b/drivers/firmware/efi/libstub/Makefile.zboot
> index 0a9dcc2b13736519..1b101d9076fd49e5 100644
> --- a/drivers/firmware/efi/libstub/Makefile.zboot
> +++ b/drivers/firmware/efi/libstub/Makefile.zboot
> @@ -40,7 +40,7 @@ quiet_cmd_compwithsize = $(quiet_cmd_$(zboot-method-y))
>  $(obj)/vmlinuz: $(obj)/vmlinux.bin FORCE
>  	$(call if_changed,compwithsize)
>  
> -OBJCOPYFLAGS_vmlinuz.o := -I binary -O $(EFI_ZBOOT_BFD_TARGET) \
> +OBJCOPYFLAGS_vmlinuz.o := -I binary -O $(EFI_ZBOOT_BFD_TARGET) $(EFI_ZBOOT_OBJCOPY_FLAGS) \
>  			  --rename-section .data=.gzdata,load,alloc,readonly,contents
>  $(obj)/vmlinuz.o: $(obj)/vmlinuz FORCE
>  	$(call if_changed,objcopy)
> diff --git a/drivers/firmware/efi/libstub/zboot.lds b/drivers/firmware/efi/libstub/zboot.lds
> index 93d33f68333b2b68..ac8c0ef851581f5d 100644
> --- a/drivers/firmware/efi/libstub/zboot.lds
> +++ b/drivers/firmware/efi/libstub/zboot.lds
> @@ -2,6 +2,8 @@
>  
>  ENTRY(__efistub_efi_zboot_header);
>  
> +PROVIDE(zboot_code_size = ABSOLUTE(0));
> +
>  SECTIONS
>  {
>  	.head : ALIGN(4096) {
> @@ -17,6 +19,11 @@ SECTIONS
>  		*(.gzdata)
>  		__efistub__gzdata_end = .;
>  		*(.rodata* .init.rodata* .srodata*)
> +
> +		. = ALIGN(4);
> +		__efistub_code_size = .;
> +		LONG(zboot_code_size);
> +
>  		_etext = ALIGN(4096);
>  		. = _etext;
>  	}
> -- 
> 2.39.2
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-04-26 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 14:11 [PATCH 0/2] arm64: Expose kernel code size to EFI zboot code Ard Biesheuvel
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 [this message]
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=ZElKHGu2Xd/mAvoo@FVFF77S0Q05N \
    --to=mark.rutland@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --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).