public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Ard Biesheuvel <ardb@kernel.org>, Gerd Hoffmann <kraxel@redhat.com>
Cc: Ard Biesheuvel <ardb@google.com>,
	devel@edk2.groups.io, Oliver Steffen <osteffen@redhat.com>,
	Alexander Graf <graf@amazon.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 v4] ArmVirt: Allow memory attributes protocol to be disabled
Date: Tue, 12 Dec 2023 16:22:55 +0100	[thread overview]
Message-ID: <95c2dd16-e490-39e1-71fc-f80ec0cd5948@redhat.com> (raw)
In-Reply-To: <CAMj1kXFf8z+g=A-mKE29PJh4azDGSZDby4vzedVfthHkeTLDUw@mail.gmail.com>

On 12/12/23 11:42, Ard Biesheuvel wrote:
> On Tue, 12 Dec 2023 at 11:08, Gerd Hoffmann <kraxel@redhat.com> wrote:
>>
>> On Tue, Dec 12, 2023 at 09:36:00AM +0100, Ard Biesheuvel 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, and a PCD to set the default for
>>> this option when it is omitted.
>>>
>>>   -fw_cfg opt/org.tianocore/UninstallMemAttrProtocol,string=y
>>
>> Tested-by: Gerd Hoffmann <kraxel@redhat.com>
>> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
>>
> 
> Thanks all - I've queued this up now.
> 

If it hasn't been merged yet, add:

Reviewed-by: Laszlo Ersek <lersek@redhat.com>

thanks
Laszlo



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



      reply	other threads:[~2023-12-12 15:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12  8:36 [edk2-devel] [PATCH v4] ArmVirt: Allow memory attributes protocol to be disabled Ard Biesheuvel
2023-12-12 10:07 ` Gerd Hoffmann
2023-12-12 10:42   ` Ard Biesheuvel
2023-12-12 15:22     ` Laszlo Ersek [this message]

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=95c2dd16-e490-39e1-71fc-f80ec0cd5948@redhat.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