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>,
	 Richard Hughes <richard@hughsie.com>,
	 James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: [GIT PULL] EFI fixes for v6.14 #2
Date: Fri, 28 Feb 2025 15:00:21 +0100	[thread overview]
Message-ID: <20250228140020.3558244-2-ardb+git@google.com> (raw)

From: Ard Biesheuvel <ardb@kernel.org>

Hi Linus,

Another couple of EFI fixes for v6.14. Only James's patch stands out, as it
implements a workaround for odd behavior in fwupd in user space, which creates
EFI variables by touching a file in efivarfs, clearing the immutable bit (which
gets set automatically for $reasons) and then opening it again for writing,
none of which is really necessary. The fwupd author and LVFS maintainer is
already rolling out a fix for this on the fwupd side, and suggested that the
workaround in this PR could be backed out again during the next cycle.

(There is a semantic mismatch in efivarfs where some essential variable
attributes are stored in the first 4 bytes of the file, and so zero length
files cannot exist, as they cannot be written back to the underlying variable
store. So now, they are dropped once the last reference is released.)

Please pull.


The following changes since commit bbc4578537e350d5bf8a7a2c7d054d6b163b3c41:

  efi: Use BIT_ULL() constants for memory attributes (2025-02-04 14:08:22 +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.14-2

for you to fetch changes up to e3cf2d91d0583cae70aeb512da87e3ade25ea912:

  efi/mokvar-table: Avoid repeated map/unmap of the same page (2025-02-27 18:25:44 +0100)

Cc: Richard Hughes <richard@hughsie.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>

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

- Fix CPER error record parsing bugs

- Fix a couple of efivarfs issues that were introduced in the merge
  window

- Fix an issue in the early remapping code of the MOKvar table

----------------------------------------------------------------
Ard Biesheuvel (2):
      efivarfs: Defer PM notifier registration until .fill_super
      efi/mokvar-table: Avoid repeated map/unmap of the same page

James Bottomley (1):
      efivarfs: allow creation of zero length files

Patrick Rudolph (2):
      efi/cper: Fix cper_ia_proc_ctx alignment
      efi/cper: Fix cper_arm_ctx_info alignment

Peter Jones (1):
      efi: Don't map the entire mokvar table to determine its size

 drivers/firmware/efi/cper-arm.c     |  2 +-
 drivers/firmware/efi/cper-x86.c     |  2 +-
 drivers/firmware/efi/mokvar-table.c | 57 ++++++++++++++++++-------------------
 fs/efivarfs/file.c                  | 10 ++++---
 fs/efivarfs/super.c                 |  3 +-
 5 files changed, 37 insertions(+), 37 deletions(-)

             reply	other threads:[~2025-02-28 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 14:00 Ard Biesheuvel [this message]
2025-02-28 17:49 ` [GIT PULL] EFI fixes for v6.14 #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=20250228140020.3558244-2-ardb+git@google.com \
    --to=ardb+git@google.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ardb@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=richard@hughsie.com \
    --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