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 13:20:42 +0200 [thread overview]
Message-ID: <20200406112042.GC2520@zn.tnic> (raw)
In-Reply-To: <CAMj1kXHAieZDvPKfjF=J+G=QVS+=XS-b4RP_=mjCEFEB_E_+Qw@mail.gmail.com>
On Mon, Apr 06, 2020 at 11:11:21AM +0200, Ard Biesheuvel wrote:
> Yes, it is in the PE/COFF specification. [0]
>
> The whole problem is that we are conflating 'loading a PE/COFF image'
> with 'copying a PE/COFF image into memory', which are not the same
> thing. It is not just the layout issue, we are running into other
> problems with things like UEFI secure boot and TPM-based measured
> boot, where the fact that omitting the standard LoadImage() boot
> service (which takes care of these things under the hood) means that
> you now have to do your own checks and measurements. These things are
> literally all over the place at the moment, shim, GRUB, systemd-boot
> etc, with no authoritative spec that describes which component should
> be doing what.
Sounds to me like what LoadImage() does is what the authoritative spec
should be. Perhaps we should write it down as "Do what LoadImage()
does... " and then enumerate the requirements.
> Commit ec93fc371f014a6fb483e3556061ecad4b40735c has the background, but ...
Nice, I like the aspect of letting firmware do only a minimum amount of
work. :)
> ... I'll look into updating the documentation as well.
Thanks!
> Note that this stuff is hot off the press, so there may be some issues
> lurking (like this one) that we hadn't thought of yet.
Right.
> Actually, it may be sufficient to #define __efistub_global to
> __section(.data) like we already do for ARM, to ensure that these
> global flags are always initialized correctly. (I'll wait for Sergey
> to confirm that the spurious enabling of the PCI DMA protection
> resulting from this BSS issue is causing the boot regression)
Cool, but let's not jinx it. :-)
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-04-06 11:20 UTC|newest]
Thread overview: 31+ 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>
2020-04-05 23:18 ` [PATCH 1/2] x86/boot/compressed/64: Remove .bss/.pgtable from bzImage Arvind Sankar
2020-04-06 0:00 ` Sergey Shatunov
2020-04-06 3:51 ` Arvind Sankar
2020-04-06 7:32 ` Ard Biesheuvel
2020-04-06 8:47 ` Borislav Petkov
2020-04-06 9:11 ` Ard Biesheuvel
2020-04-06 11:20 ` Borislav Petkov [this message]
2020-04-06 13:22 ` Arvind Sankar
2020-04-06 13:29 ` Ard Biesheuvel
2020-04-06 16:01 ` Arvind Sankar
2020-04-06 16:22 ` Ard Biesheuvel
2020-04-06 16:52 ` Arvind Sankar
2020-04-06 16:59 ` Ard Biesheuvel
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
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
2020-04-08 7:49 ` Ard Biesheuvel
2020-04-09 14:39 ` Arvind Sankar
2020-04-09 14:47 ` Ard Biesheuvel
2020-04-09 16:35 ` Arvind Sankar
2020-04-10 14:47 ` Arvind Sankar
2020-04-10 15:26 ` Ard Biesheuvel
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
2020-04-06 8:44 ` Ard Biesheuvel
2020-04-06 12:36 ` Sergey Shatunov
2020-04-06 13:20 ` Ard Biesheuvel
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=20200406112042.GC2520@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;
as well as URLs for NNTP newsgroup(s).