From: Ard Biesheuvel <ardb+git@google.com>
To: torvalds@linux-foundation.org
Cc: linux-efi@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: [GIT PULL] EFI fixes for v6.9 #2
Date: Sun, 24 Mar 2024 21:52:35 +0100 [thread overview]
Message-ID: <20240324205235.3988845-2-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
Hi Linus,
A steady trickle of EFI fixes this cycle - this is due to the backports hitting
kernels that are more widely used. There are a few more issues under
investigation, but these fixes are straight-forward and important, so no need
to delay them.
Please pull.
The following changes since commit b3810c5a2cc4a6665f7a65bed5393c75ce3f3aa2:
x86/efistub: Clear decompressor BSS in native EFI entrypoint (2024-03-15 19:47:09 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-fixes-for-v6.9-2
for you to fetch changes up to 62b71cd73d41ddac6b1760402bbe8c4932e23531:
efi: fix panic in kdump kernel (2024-03-24 09:28:33 +0100)
----------------------------------------------------------------
EFI fixes for v6.9 #2
- Fix logic that is supposed to prevent placement of the kernel image
below LOAD_PHYSICAL_ADDR
- Use the firmware stack in the EFI stub when running in mixed mode
- Clear BSS only once when using mixed mode
- Check efi.get_variable() function pointer for NULL before trying to
call it
----------------------------------------------------------------
Ard Biesheuvel (2):
x86/efistub: Call mixed mode boot services on the firmware's stack
x86/efistub: Don't clear BSS twice in mixed mode
KONDO KAZUMA(近藤 和真) (1):
efi/libstub: fix efi_random_alloc() to allocate memory at alloc_min or higher address
Oleksandr Tymoshenko (1):
efi: fix panic in kdump kernel
arch/x86/boot/compressed/efi_mixed.S | 9 +++++++++
drivers/firmware/efi/efi.c | 2 ++
drivers/firmware/efi/libstub/randomalloc.c | 2 +-
drivers/firmware/efi/libstub/x86-stub.c | 3 ++-
4 files changed, 14 insertions(+), 2 deletions(-)
next reply other threads:[~2024-03-24 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 20:52 Ard Biesheuvel [this message]
2024-03-24 21:02 ` [GIT PULL] EFI fixes for v6.9 #2 pr-tracker-bot
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=20240324205235.3988845-2-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=torvalds@linux-foundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).