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 #2
Date: Thu, 15 Jan 2026 18:26:11 +0100	[thread overview]
Message-ID: <20260115172610.1844636-2-ardb+git@google.com> (raw)

From: Ard Biesheuvel <ardb@kernel.org>

Hi Linus,

Please pull the EFI fixes below:


The following changes since commit cfe54f4591e675cedf2c0d25287ff4c0a2e0cb9d:

  kthread: Warn if mm_struct lacks user_ns in kthread_use_mm() (2025-12-24 21:32:58 +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.19-2

for you to fetch changes up to d7f1b4bdc7108be1b178e1617b5f45c8918e88d7:

  efi/cper: Fix cper_bits_to_str buffer handling and return value (2026-01-14 11:34:42 +0100)

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

- Wipe the INITRD config table upon consumption so it doesn't confuse
  kexec

- Let APEI/GHES maintainers take responsibility for CPER processing
  logic

- Fix wrong return value in CPER string helper routine

----------------------------------------------------------------
Ard Biesheuvel (1):
      efi: Wipe INITRD config table from memory after consumption

Mauro Carvalho Chehab (1):
      MAINTAINERS: add cper to APEI files

Morduan Zang (1):
      efi/cper: Fix cper_bits_to_str buffer handling and return value

 MAINTAINERS                 | 2 ++
 drivers/firmware/efi/cper.c | 2 +-
 drivers/firmware/efi/efi.c  | 1 +
 3 files changed, 4 insertions(+), 1 deletion(-)

             reply	other threads:[~2026-01-15 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15 17:26 Ard Biesheuvel [this message]
2026-01-15 20:09 ` [GIT PULL] EFI fixes for v6.19 #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=20260115172610.1844636-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