public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Alexander Graf via groups.io" <graf=amazon.com@groups.io>
To: Ard Biesheuvel <ardb@kernel.org>, Ard Biesheuvel <ardb@google.com>
Cc: <devel@edk2.groups.io>, Laszlo Ersek <lersek@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Oliver Steffen <osteffen@redhat.com>,
	Oliver Smith-Denny <osde@linux.microsoft.com>,
	Taylor Beebe <taylor.d.beebe@gmail.com>,
	"Peter Jones" <pjones@redhat.com>,
	Leif Lindholm <quic_llindhol@quicinc.com>
Subject: Re: [edk2-devel] [PATCH v2] ArmVirt: Allow memory attributes protocol to be disabled on first boot
Date: Mon, 11 Dec 2023 01:02:36 +0100	[thread overview]
Message-ID: <ee7b2795-ca09-41da-9d73-2bf92f605c2b@amazon.com> (raw)
In-Reply-To: <CAMj1kXGVTJCAH3j7wXsu8-=iRYWPB-AzDKSmCinwjmJv_DX_mQ@mail.gmail.com>


On 08.12.23 12:20, Ard Biesheuvel wrote:
> On Thu, 7 Dec 2023 at 11:06, Ard Biesheuvel <ardb@google.com> wrote:
>> From: Ard Biesheuvel <ardb@kernel.org>
>>
>> Shim's PE loader uses the EFI memory attributes protocol in a way that
>> results in an immediate crash when invoking the loaded image, unless the
>> base and size of its executable segment are both aligned to 4k.
>>
>> If this is not the case, it will strip the memory allocation of its
>> executable permissions, but fail to add them back for the executable
>> region, resulting in non-executable code. Unfortunately, the PE loader
>> does not even bother invoking the protocol in this case (as it notices
>> the misalignment), making it very hard for system firmware to work
>> around this by attempting to infer the intent of the caller.
>>
>> So let's introduce a QEMU command line option to indicate that the
>> protocol should not be exposed at all on the first boot, which is when
>> the issue is triggered. (fbaa64.efi is broken but grubaa64.efi boots
>> fine)
>>
>>    -fw_cfg opt/org.tianocore/UninstallMemAttrProtocolOnFirstBoot,string=y
>>
>> Also introduce a fixed boolean PCD that sets the default.
>>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Cc: Gerd Hoffmann <kraxel@redhat.com>
>> Cc: Oliver Steffen <osteffen@redhat.com>
>> Cc: Alexander Graf <graf@amazon.com>
>> Cc: Oliver Smith-Denny <osde@linux.microsoft.com>
>> Cc: Taylor Beebe <taylor.d.beebe@gmail.com>
>> Cc: Peter Jones <pjones@redhat.com>
>> Cc: Leif Lindholm <quic_llindhol@quicinc.com>
>> Link: https://gitlab.com/qemu-project/qemu/-/issues/1990
>> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> OK, if nobody has problems with this approach, I intend to merge it
> and give a snapshot build to the lima folks to incorporate in their
> scripts.


No concerns from me :)

Alex





Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879




-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112264): https://edk2.groups.io/g/devel/message/112264
Mute This Topic: https://groups.io/mt/103031504/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-12-11  0:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 10:06 [edk2-devel] [PATCH v2] ArmVirt: Allow memory attributes protocol to be disabled on first boot Ard Biesheuvel
2023-12-08 11:20 ` Ard Biesheuvel
2023-12-11  0:02   ` Alexander Graf via groups.io [this message]
2023-12-08 14:34 ` Laszlo Ersek
2023-12-08 14:49   ` Laszlo Ersek
2023-12-08 15:34   ` Ard Biesheuvel
2023-12-11 14:27     ` Laszlo Ersek
2023-12-11  9:05 ` Gerd Hoffmann
2023-12-11  9:25   ` Ard Biesheuvel
2023-12-11  9:59     ` Gerd Hoffmann

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-list 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=ee7b2795-ca09-41da-9d73-2bf92f605c2b@amazon.com \
    --to=devel@edk2.groups.io \
    /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