All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, Peter Jones <pjones@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Heinrich Schuchardt <heinrich.schuchardt@gmx.de>
Subject: Re: [PATCH] efi: Fix .data section size calculations when .sbat is present
Date: Fri, 20 Jun 2025 10:19:48 +0200	[thread overview]
Message-ID: <874iwaq0yj.fsf@redhat.com> (raw)
In-Reply-To: <CAMj1kXFq+oVwuHhkCxYG5mhpeS1fStRURSg5i6+wLo-rxi=Phg@mail.gmail.com>

Ard Biesheuvel <ardb@kernel.org> writes:

> On Thu, 19 Jun 2025 at 17:29, Ard Biesheuvel <ardb@kernel.org> wrote:
>>
>> On Wed, 18 Jun 2025 at 14:20, Vitaly Kuznetsov <vkuznets@redhat.com> wrote:
>> >
>> > Commit 0f9a1739dd0e ("efi: zboot specific mechanism for embedding SBAT
>> > section") neglected to adjust the sizes of the .data section when
>> > CONFIG_EFI_SBAT_FILE is set. As the result, the produced PE binary is
>> > incorrect and some tools complain about it. E.g. 'sbsign' reports:
>> >
>> >  # sbsign --key my.key --cert my.crt arch/arm64/boot/vmlinuz.efi
>> >  warning: file-aligned section .data extends beyond end of file
>> >  warning: checksum areas are greater than image size. Invalid section table?
>> >
>> > Note, '__data_size' was also used in the PE optional header. The field is
>> > supposed to reflect "The size of the initialized data section, or the sum
>> > of all such sections if there are multiple data sections.". While OVMF
>> > based firmware doesn't seem to care much about what's there, it sounds like
>> > including .sbat in the calculation is more correct.
>> >
>> > Fixes: 0f9a1739dd0e ("efi: zboot specific mechanism for embedding SBAT section")
>> > Reported-by: Heinrich Schuchardt <heinrich.schuchardt@gmx.de>
>> > Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>> > ---
>> >  drivers/firmware/efi/libstub/zboot-header.S | 2 +-
>> >  drivers/firmware/efi/libstub/zboot.lds      | 6 ++++--
>> >  2 files changed, 5 insertions(+), 3 deletions(-)
>> >
>>
>> Thanks for the fix.
>>
>> > diff --git a/drivers/firmware/efi/libstub/zboot-header.S b/drivers/firmware/efi/libstub/zboot-header.S
>> > index b6431edd0fc9..65df5f52e138 100644
>> > --- a/drivers/firmware/efi/libstub/zboot-header.S
>> > +++ b/drivers/firmware/efi/libstub/zboot-header.S
>> > @@ -41,7 +41,7 @@ __efistub_efi_zboot_header:
>> >         .short          .Lpe_opt_magic
>> >         .byte           0, 0
>> >         .long           _etext - .Lefi_header_end
>> > -       .long           __data_size
>> > +       .long           __all_data_size
>>
>> Frankly, I'm not sure if this is even worth the hassle.
>>
>> There is also a 'size of uninitialized data' field, but given that the
>> .data section has both initialized data and uninitialized data, and
>> the fact that no loaders appear to care about these fields, let's just
>> not bother.
>>
>
> ... or add .sbat to SizeOfCode instead. (the preceding field)
>

I was wondering how to make it consistent with yet-unmerged x86
patch. In v3:
https://lore.kernel.org/linux-efi/20250603091951.57775-1-vkuznets@redhat.com/
.sbat was accounted as SizeOfCode but the section is
"IMAGE_SCN_CNT_INITIALIZED_DATA", not "IMAGE_SCN_CNT_CODE" so I sent v4
yesterday:
https://lore.kernel.org/linux-efi/20250619151759.355893-1-vkuznets@redhat.com/
which made .sbat accounted in SizeOfInitializedData.

-- 
Vitaly


  reply	other threads:[~2025-06-20  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 12:20 [PATCH] efi: Fix .data section size calculations when .sbat is present Vitaly Kuznetsov
2025-06-19 15:29 ` Ard Biesheuvel
2025-06-20  5:51   ` Ard Biesheuvel
2025-06-20  8:19     ` Vitaly Kuznetsov [this message]
2025-06-20 10:29       ` Ard Biesheuvel
2025-06-20 10:58         ` Vitaly Kuznetsov

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=874iwaq0yj.fsf@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=ardb@kernel.org \
    --cc=heinrich.schuchardt@gmx.de \
    --cc=kraxel@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=pjones@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.