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.8 #2
Date: Fri, 1 Mar 2024 10:51:27 +0100 [thread overview]
Message-ID: <20240301095126.1223559-2-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
Hello Linus,
Please pull the EFI fixes below. Only the EFI variable name size change is
significant, and will be backported once it lands. The others are cleanup.
The following changes since commit 1ad55cecf22f05f1c884adf63cc09d3c3e609ebf:
x86/efistub: Use 1:1 file:memory mapping for PE/COFF .compat section (2024-02-05 10:24:51 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-fixes-for-v6.8-2
for you to fetch changes up to 2ce507f57ba9c78c080d4a050ebdc97263239de8:
efivarfs: Drop 'duplicates' bool parameter on efivar_init() (2024-02-25 09:43:39 +0100)
----------------------------------------------------------------
EFI fixes for v6.8 #2
- Fix phys_addr_t size confusion in 32-bit capsule loader
- Reduce maximum EFI variable name size to 512 to work around buggy
firmware
- Drop some redundant code from efivarfs while at it
----------------------------------------------------------------
Ard Biesheuvel (2):
efivarfs: Drop redundant cleanup on fill_super() failure
efivarfs: Drop 'duplicates' bool parameter on efivar_init()
Arnd Bergmann (1):
efi/capsule-loader: fix incorrect allocation size
Tim Schumacher (1):
efivarfs: Request at most 512 bytes for variable names
drivers/firmware/efi/capsule-loader.c | 2 +-
fs/efivarfs/internal.h | 2 +-
fs/efivarfs/super.c | 7 +------
fs/efivarfs/vars.c | 23 +++++++++++++----------
4 files changed, 16 insertions(+), 18 deletions(-)
next reply other threads:[~2024-03-01 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 9:51 Ard Biesheuvel [this message]
2024-03-01 20:17 ` [GIT PULL] EFI fixes for v6.8 #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=20240301095126.1223559-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).