public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, osy@turing.llc
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Gerd Hoffmann <kraxel@redhat.com>,
	 Leif Lindholm <quic_llindhol@quicinc.com>,
	dann frazier <dann.frazier@canonical.com>
Subject: Re: [edk2-devel] ArmVirtPkg: non-executable EFI_LOADER_DATA breaks GRUB on Ubuntu 22.04
Date: Mon, 10 Jul 2023 16:58:15 +0100	[thread overview]
Message-ID: <CAKbZUD3xob5az6W=zzu7RVijD42HgXoAp+XJeEWNc7KSzEtytA@mail.gmail.com> (raw)
In-Reply-To: <G5uU.1688851011402113527.gj7D@groups.io>

On Mon, Jul 10, 2023 at 2:28 PM <osy@turing.llc> wrote:
>
> I have an existing install of Ubuntu 22.04 on a QEMU virtual machine which I've decided to update the UEFI firmware. After doing so, GRUB no longer boots ("Synchronous Exception" message seen). After a git bisect session, I found the problematic 2997ae38739756ecba9b0de19e86032ebc689ef9. The comment says GRUB should have been fixed in 2017, but for one reason or another, my VM which was built in 2022 still had the issue. Regardless, I don't think it's a good idea to break GRUB, even if it's fixed in 2017. In the very least, a better error message would be preferable to crashing with an "Synchronous Exception." Googling this error message shows that other people may be hitting this issue as well but the vague error symptom means its impossible to know if it's the same issue or not.

+CC Some of the folks involved in the original discussion

In the original thread, people discussed some alternative behavior to
just crashing on a NX fault. Is this still an alternative?
I'm kind of thinking this should be addressed by distros anyway....
How is $CURRENT_YEAR Ubuntu still shipping bad GRUBs? I know the
situation around GRUB and distro patching is complicated but...
Do we have any idea of how many distros/GRUBs are affected by this?

Personally, I would like to avoid loosening up memory permissions.

--
Pedro

  reply	other threads:[~2023-07-10 15:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08 21:16 ArmVirtPkg: non-executable EFI_LOADER_DATA breaks GRUB on Ubuntu 22.04 osy
2023-07-10 15:58 ` Pedro Falcato [this message]
2023-07-10 17:09   ` [edk2-devel] " osy
2023-07-11  6:58   ` Gerd Hoffmann
2023-07-13 16:57     ` Pedro Falcato
2023-07-13 17:20       ` Ard Biesheuvel
2023-07-13 17:41         ` Pedro Falcato
2023-07-13 18:22           ` Oliver Smith-Denny
2023-07-13 23:03             ` Michael D Kinney
2023-07-17  9:30       ` 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='CAKbZUD3xob5az6W=zzu7RVijD42HgXoAp+XJeEWNc7KSzEtytA@mail.gmail.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