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.10 #1
Date: Tue, 21 May 2024 19:13:04 +0200 [thread overview]
Message-ID: <20240521171303.3822496-2-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
Hi Linus,
Please pull the fix below. This is going be backported to v6.1 and later to
address the regression described in the commit. Whether or not physical KASLR
for the cases in question will be brought back later (presumably by sharing the
physical placement logic with the traditional decompressor) is as yet
undecided.
The following changes since commit 4b2543f7e1e6b91cfc8dd1696e3cdf01c3ac8974:
efi: libstub: only free priv.runtime_map when allocated (2024-04-29 17:47:32 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-fixes-for-v6.10-1
for you to fetch changes up to 15aa8fb852f995dd234a57f12dfb989044968bb6:
x86/efistub: Omit physical KASLR when memory reservations exist (2024-05-17 17:06:18 +0200)
----------------------------------------------------------------
EFI fixes for v6.10 #1
- Followup fix for the EFI boot sequence refactor, which may result in
physical KASLR putting the kernel in a region which is being used for
a special purpose via a command line argument.
----------------------------------------------------------------
Ard Biesheuvel (1):
x86/efistub: Omit physical KASLR when memory reservations exist
drivers/firmware/efi/libstub/x86-stub.c | 28 ++++++++++++++++++++++++++--
1 file changed, 26 insertions(+), 2 deletions(-)
next reply other threads:[~2024-05-21 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 17:13 Ard Biesheuvel [this message]
2024-05-21 18:53 ` [GIT PULL] EFI fixes for v6.10 #1 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=20240521171303.3822496-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.