Linux EFI development
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@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.7 #2
Date: Wed, 13 Dec 2023 15:51:22 +0100	[thread overview]
Message-ID: <20231213145121.2935172-2-ardb@google.com> (raw)

From: Ard Biesheuvel <ardb@kernel.org>

Hi Linus,

Please pull the EFI fixes below.

The following changes since commit 01b1e3ca0e5ce47bbae8217d47376ad01b331b07:

  efi/unaccepted: Fix off-by-one when checking for overlapping ranges (2023-11-28 12:49:21 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent-for-v6.7-2

for you to fetch changes up to 50d7cdf7a9b1ab6f4f74a69c84e974d5dc0c1bf1:

  efi/x86: Avoid physical KASLR on older Dell systems (2023-12-11 17:57:42 +0100)

----------------------------------------------------------------
EFI fixes for v6.7 #2

- Deal with a regression in the recently refactored x86 EFI stub code on
  older Dell systems by disabling randomization of the physical load
  address
- Use the correct load address for relocatable Loongarch kernels

----------------------------------------------------------------
Ard Biesheuvel (1):
      efi/x86: Avoid physical KASLR on older Dell systems

Wang Yao (1):
      efi/loongarch: Use load address to calculate kernel entry address

 arch/loongarch/include/asm/efi.h              |  2 +-
 drivers/firmware/efi/libstub/loongarch-stub.c |  4 ++--
 drivers/firmware/efi/libstub/loongarch.c      |  6 +++---
 drivers/firmware/efi/libstub/x86-stub.c       | 31 +++++++++++++++++++++------
 4 files changed, 30 insertions(+), 13 deletions(-)

             reply	other threads:[~2023-12-13 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 14:51 Ard Biesheuvel [this message]
2023-12-13 19:32 ` [GIT PULL] EFI fixes for v6.7 #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=20231213145121.2935172-2-ardb@google.com \
    --to=ardb@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