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 updates for v6.8
Date: Sun, 7 Jan 2024 12:43:45 +0100 [thread overview]
Message-ID: <20240107114345.3415677-2-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
Hi Linus,
Please consider the EFI pull request below. There is some new stuff as well as
some low-urgency fixes, which may be backported later.
The following changes since commit 50d7cdf7a9b1ab6f4f74a69c84e974d5dc0c1bf1:
efi/x86: Avoid physical KASLR on older Dell systems (2023-12-11 17:57:42 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-next-for-v6.8
for you to fetch changes up to 4afa688d7141ae7a166d32224abbfd536acccfca:
efi: memmap: fix kernel-doc warnings (2023-12-22 10:42:06 +0100)
----------------------------------------------------------------
EFI updates for v6.8
- Fix a syzbot reported issue in efivarfs where concurrent accesses to
the file system resulted in list corruption
- Add support for accessing EFI variables via the TEE subsystem (and a
trusted application in the secure world) instead of via EFI runtime
firmware running in the OS's execution context
- Avoid linker tricks to discover the image base on LoongArch
----------------------------------------------------------------
Ard Biesheuvel (4):
efivarfs: Move efivar availability check into FS context init
efivarfs: Free s_fs_info on unmount
efivarfs: Move efivarfs list into superblock s_fs_info
Merge branch 'efi/urgent' into efi/next
Ilias Apalodimas (1):
efivarfs: force RO when remounting if SetVariable is not supported
Masahisa Kojima (4):
efi: expose efivar generic ops register function
efi: Add EFI_ACCESS_DENIED status code
efi: Add tee-based EFI variable driver
efivarfs: automatically update super block flag
Randy Dunlap (1):
efi: memmap: fix kernel-doc warnings
Wang Yao (1):
efi/loongarch: Directly position the loaded image file
arch/loongarch/include/asm/efi.h | 2 -
arch/loongarch/kernel/head.S | 1 -
arch/loongarch/kernel/image-vars.h | 1 -
arch/loongarch/kernel/vmlinux.lds.S | 1 -
drivers/firmware/efi/Kconfig | 15 +
drivers/firmware/efi/Makefile | 1 +
drivers/firmware/efi/efi.c | 18 +
drivers/firmware/efi/libstub/loongarch-stub.c | 9 +-
drivers/firmware/efi/libstub/loongarch-stub.h | 4 +
drivers/firmware/efi/libstub/loongarch.c | 6 +-
drivers/firmware/efi/memmap.c | 8 +-
drivers/firmware/efi/stmm/mm_communication.h | 236 ++++++++++
drivers/firmware/efi/stmm/tee_stmm_efi.c | 616 ++++++++++++++++++++++++++
drivers/firmware/efi/vars.c | 8 +
fs/efivarfs/inode.c | 3 +-
fs/efivarfs/internal.h | 8 +-
fs/efivarfs/super.c | 66 ++-
fs/efivarfs/vars.c | 5 +-
include/linux/efi.h | 12 +
19 files changed, 987 insertions(+), 33 deletions(-)
create mode 100644 drivers/firmware/efi/libstub/loongarch-stub.h
create mode 100644 drivers/firmware/efi/stmm/mm_communication.h
create mode 100644 drivers/firmware/efi/stmm/tee_stmm_efi.c
next reply other threads:[~2024-01-07 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 11:43 Ard Biesheuvel [this message]
2024-01-10 1:31 ` [GIT PULL] EFI updates for v6.8 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=20240107114345.3415677-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).