From: Ard Biesheuvel <ardb@kernel.org>
To: linux-efi@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ardb@kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: [PATCH v3 0/4] efi/arm64: work around Image placement issues
Date: Mon, 26 Jul 2021 16:51:52 +0200 [thread overview]
Message-ID: <20210726145156.12006-1-ardb@kernel.org> (raw)
Ben reported that distro GRUB may fail to boot in some circumstances,
and tracked it down to an issue in the way distro GRUB allocates space
for the image. Due to an oversight (addressed in patch #2), this
condition is rarely triggered, but let's work around it in any case (#1)
Remaining patches add further warnings for conditions that are unlikely
to occur, but should not be ignored.
Build tested only.
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Ard Biesheuvel (4):
efi/libstub: arm64: Force Image reallocation if BSS was not reserved
efi/libstub: arm64: Relax 2M alignment again for relocatable kernels
efi/libstub: arm64: Warn when efi_random_alloc() fails
efi/libstub: arm64: Double check image alignment at entry
drivers/firmware/efi/libstub/arm64-stub.c | 71 +++++++++++++++++---
1 file changed, 61 insertions(+), 10 deletions(-)
--
2.20.1
next reply other threads:[~2021-07-26 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 14:51 Ard Biesheuvel [this message]
2021-07-26 14:51 ` [PATCH v3 1/4] efi/libstub: arm64: Force Image reallocation if BSS was not reserved Ard Biesheuvel
2021-07-26 14:51 ` [PATCH v3 2/4] efi/libstub: arm64: Relax 2M alignment again for relocatable kernels Ard Biesheuvel
2021-07-26 14:51 ` [PATCH v3 3/4] efi/libstub: arm64: Warn when efi_random_alloc() fails Ard Biesheuvel
2021-07-26 14:51 ` [PATCH v3 4/4] efi/libstub: arm64: Double check image alignment at entry Ard Biesheuvel
2021-08-02 11:26 ` [PATCH v3 0/4] efi/arm64: work around Image placement issues Benjamin Herrenschmidt
2021-08-02 12:03 ` 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=20210726145156.12006-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.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).