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.14 #3
Date: Thu, 20 Mar 2025 07:37:47 +0100 [thread overview]
Message-ID: <20250320063746.4177561-2-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
Hi Linus,
Here's a final batch of EFI fixes for v6.14. The efivarfs ones are fixes for
changes that were made this cycle. James's fix is somewhat of a band-aid, but
it was blessed by the VFS folks, who are working with James to come up with
something better for the next cycle.
Please pull.
The following changes since commit e3cf2d91d0583cae70aeb512da87e3ade25ea912:
efi/mokvar-table: Avoid repeated map/unmap of the same page (2025-02-27 18:25:44 +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-3
for you to fetch changes up to 11092db5b57377ac99e6339cfd16ca35ef011f3c:
efivarfs: fix NULL dereference on resume (2025-03-18 08:46:08 +0100)
----------------------------------------------------------------
EFI fixes for v6.14 #3
- Avoid physical address 0x0 for random page allocations
- Add correct lockdep annotation when traversing efivarfs on resume
- Avoid NULL mount in kernel_file_open() when traversing efivarfs on
resume
----------------------------------------------------------------
Ard Biesheuvel (2):
efi/libstub: Avoid physical address 0x0 when doing random allocation
efivarfs: use I_MUTEX_CHILD nested lock to traverse variables on resume
James Bottomley (1):
efivarfs: fix NULL dereference on resume
drivers/firmware/efi/libstub/randomalloc.c | 4 +++
fs/efivarfs/super.c | 52 ++++++++++++++++++++++++++++--
2 files changed, 53 insertions(+), 3 deletions(-)
next reply other threads:[~2025-03-20 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 6:37 Ard Biesheuvel [this message]
2025-03-20 17:02 ` [GIT PULL] EFI fixes for v6.14 #3 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=20250320063746.4177561-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