public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] efi: x86: Make the deprecated EFI handover protocol optional
Date: Sat, 8 Oct 2022 17:51:30 +0200	[thread overview]
Message-ID: <Y0GcZQZTaCgoNFGa@nazgul.tnic> (raw)
In-Reply-To: <CAMj1kXHK_9iDT8CSHnZ15yB+Z=+haZXjbQ99m20jQUr0NScK4Q@mail.gmail.com>

On Sat, Oct 08, 2022 at 05:41:40PM +0200, Ard Biesheuvel wrote:
> Yeah most distros have ~100 ore more patches against GRUB, but this
> isn't actually their fault. GRUB maintainership was defunct for a
> number of years, which is why we were stuck on GRUB version 2.02-beta3
> for such a long time. But in recent years, things have been getting
> better, and there is an agreement with the current maintainer not to
> merge the EFI handover protocol, and merge the new EFI protocol based
> initrd loading method instead, which works on all architectures
> instead of only on x86.

Aha, ok.

> Never tried that in .S files but I guess it should just work.

If not, at least in the .c files.

> I'd venture a guess that this will break the boot even your own x86
> boxes, given that almost nobody uses plain upstream GRUB..
> 
> I can work with the distros directly to start disabling this in their
> downstream configs once their GRUB builds are up to date with the new
> changes, so we can phase this out in a controlled manner.

Hm, that might turn out to be a multi-year effort considering how the
enterprise distros' kernels are moving. Yeah, yeah, they have good
reasons and so on.

> But disabling tthis right now by default is going to affect everyone
> who builds their own kernels and runs them on a distro Linux install.

Ok, I can try it on my SUSE and Debian partitions and see what happens.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2022-10-08 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 17:29 [PATCH] efi: x86: Make the deprecated EFI handover protocol optional Ard Biesheuvel
2022-10-08 14:51 ` Borislav Petkov
2022-10-08 15:41   ` Ard Biesheuvel
2022-10-08 15:51     ` Borislav Petkov [this message]
2022-10-10  8:59       ` Ard Biesheuvel
2022-10-10  9:21         ` Borislav Petkov

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=Y0GcZQZTaCgoNFGa@nazgul.tnic \
    --to=bp@alien8.de \
    --cc=ardb@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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