From: Borislav Petkov <bp@alien8.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Arvind Sankar <nivedita@alum.mit.edu>,
Sergey Shatunov <me@prok.pw>,
hpa@zytor.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mingo@redhat.com, Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-efi <linux-efi@vger.kernel.org>,
initramfs@vger.kernel.org,
Donovan Tremura <neurognostic@protonmail.ch>,
Harald Hoyer <harald@hoyer.xyz>
Subject: Re: [PATCH 1/2] x86/boot/compressed/64: Remove .bss/.pgtable from bzImage
Date: Mon, 6 Apr 2020 10:47:38 +0200 [thread overview]
Message-ID: <20200406084738.GA2520@zn.tnic> (raw)
In-Reply-To: <CAMj1kXEUhyv886CjyKvjw2F12WaZxZRUWF6t_XzP4C2TJPdpeg@mail.gmail.com>
On Mon, Apr 06, 2020 at 09:32:47AM +0200, Ard Biesheuvel wrote:
> The EFI handover protocol strikes again :-(
>
> It seems we did not include any guidance in the documentation in
> Documentation/x86/boot.rst regarding zero-initializing BSS, and come
> to think of it, we don't include any other requirements either, i.e.,
> regarding placement wrt section alignment etc. This is a serious bug.
> Even though EFI usually lays out PE/COFF images in files the exact way
> they appear in memory, this is not actually required by the spec. Most
> notably, the virtual size can be smaller than the file size, and the
> loader is expected to zero-initialize the difference as well.
Is that expectation stated explicitly somewhere?
> Since the EFI handover protocol should be considered deprecated at
> this point (and is never going to be supported in upstream GRUB
> either, for instance), I would recommend the systemd-boot developers
> to start looking into deprecating this as well, and switch to the
> ordinary PE/COFF entry point, and use the new initrd callback protocol
> for initrd loading.
Any pointers to that new initrd callback protocol?
In any case, I'd really appreciate a patch to boot.rst formulating those
requirements so that they're written down and people can find them.
> On the Linux/x86 side, we should at least add some code to the EFI
> handover protocol entry point to zero initialize BSS, and ensure that
> it is either not needed in other places, or add the code to deal with
> those as well.
Sounds like a simple fix, if that would fix it.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-04-06 8:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200109150218.16544-1-nivedita@alum.mit.edu>
[not found] ` <20200405154245.11972-1-me@prok.pw>
[not found] ` <20200405231845.GA3095309@rani.riverdale.lan>
[not found] ` <c692eea9213172d8ef937322b02ff585b0dfea82.camel@prok.pw>
[not found] ` <c692eea9213172d8ef937322b02ff585b0dfea82.camel-fHUSW+XspFU@public.gmane.org>
2020-04-06 3:51 ` [PATCH 1/2] x86/boot/compressed/64: Remove .bss/.pgtable from bzImage Arvind Sankar
2020-04-06 7:32 ` Ard Biesheuvel
2020-04-06 8:47 ` Borislav Petkov [this message]
[not found] ` <20200406084738.GA2520-Jj63ApZU6fQ@public.gmane.org>
2020-04-06 9:11 ` Ard Biesheuvel
[not found] ` <CAMj1kXHAieZDvPKfjF=J+G=QVS+=XS-b4RP_=mjCEFEB_E_+Qw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-04-06 11:20 ` Borislav Petkov
2020-04-06 13:22 ` Arvind Sankar
[not found] ` <20200406132215.GA113388-ZaHV2fEG+eCZQHugZx4kin66tl449arB@public.gmane.org>
2020-04-06 13:29 ` Ard Biesheuvel
[not found] ` <CAMj1kXG+34-bK1XuxX5VopkRt1SV1ewUAEmif+aQj5cJQ=9vbA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-04-06 16:01 ` Arvind Sankar
[not found] ` <20200406160148.GB113388-ZaHV2fEG+eCZQHugZx4kin66tl449arB@public.gmane.org>
2020-04-06 16:22 ` Ard Biesheuvel
[not found] ` <CAMj1kXFKDWB9n0kWhXHLH0XP0O1v_0b=bFJad=kBvx2qVxqDcQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-04-06 16:52 ` Arvind Sankar
2020-04-06 16:59 ` Ard Biesheuvel
[not found] ` <CAMj1kXEUkJ1XJ9OTsijeq8tNNYC00bXqEV44OMtX5ugo9WoLKA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-04-06 18:06 ` [PATCH 1/2] efi/x86: Move efi stub globals from .bss to .data Arvind Sankar
2020-04-06 18:06 ` [PATCH 2/2] efi/x86: Always relocate the kernel for EFI handover entry Arvind Sankar
[not found] ` <20200406180614.429454-1-nivedita-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2020-04-06 18:29 ` [PATCH 1/2] efi/x86: Move efi stub globals from .bss to .data Ard Biesheuvel
2020-04-08 7:43 ` Dave Young
[not found] ` <20200408074334.GA21886-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2020-04-08 7:49 ` Ard Biesheuvel
2020-04-09 14:39 ` Arvind Sankar
2020-04-09 14:47 ` Ard Biesheuvel
[not found] ` <CAMj1kXEm=E6B+kjZktG=sBPLQ=_HFfUz6KFLskNGzRnuMjn0gA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-04-09 16:35 ` Arvind Sankar
[not found] ` <20200409163530.GA785575-ZaHV2fEG+eCZQHugZx4kin66tl449arB@public.gmane.org>
2020-04-10 14:47 ` Arvind Sankar
2020-04-10 15:26 ` Ard Biesheuvel
[not found] ` <CAMj1kXHMQgnmdoA+qKLGa=gYg4J2p-DU3-K1LiM=AT61pi+Fvw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-04-14 14:57 ` Daniel Kiper
2020-04-10 11:26 ` Thomas Meyer
2020-04-10 14:38 ` Arvind Sankar
2020-04-11 8:50 ` Thomas Meyer
2020-04-06 17:21 ` [PATCH 1/2] x86/boot/compressed/64: Remove .bss/.pgtable from bzImage 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=20200406084738.GA2520@zn.tnic \
--to=bp@alien8.de \
--cc=ardb@kernel.org \
--cc=harald@hoyer.xyz \
--cc=hpa@zytor.com \
--cc=initramfs@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@prok.pw \
--cc=mingo@redhat.com \
--cc=neurognostic@protonmail.ch \
--cc=nivedita@alum.mit.edu \
--cc=tglx@linutronix.de \
--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