public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
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.19 #1
Date: Fri, 26 Dec 2025 18:00:40 +0100	[thread overview]
Message-ID: <20251226170040.2335976-2-ardb+git@google.com> (raw)

From: Ard Biesheuvel <ardb@kernel.org>

Hi Linus,

Details are in the tag. Please pull.


The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:

  Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-fixes-for-v6.19-1

for you to fetch changes up to cfe54f4591e675cedf2c0d25287ff4c0a2e0cb9d:

  kthread: Warn if mm_struct lacks user_ns in kthread_use_mm() (2025-12-24 21:32:58 +0100)

----------------------------------------------------------------
EFI fixes for v6.19 #1

A couple of fixes for EFI regressions introduced this cycle:

- Make EDID handling in the EFI stub mixed mode safe

- Ensure that efi_mm.user_ns has a sane value - this is needed now that
  EFI runtime calls are preemptible on arm64

----------------------------------------------------------------
Breno Leitao (2):
      arm64: efi: Fix NULL pointer dereference by initializing user_ns
      kthread: Warn if mm_struct lacks user_ns in kthread_use_mm()

Hans de Goede (1):
      efi/libstub: gop: Fix EDID support in mixed-mode

 drivers/firmware/efi/efi.c         | 1 +
 drivers/firmware/efi/libstub/gop.c | 8 ++++----
 kernel/kthread.c                   | 1 +
 3 files changed, 6 insertions(+), 4 deletions(-)

             reply	other threads:[~2025-12-26 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-26 17:00 Ard Biesheuvel [this message]
2025-12-27  0:20 ` [GIT PULL] EFI fixes for v6.19 #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=20251226170040.2335976-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