From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
linux-efi@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] EFI changes for v5.10
Date: Mon, 12 Oct 2020 17:21:19 +0200 [thread overview]
Message-ID: <20201012152119.GA3476595@gmail.com> (raw)
Linus,
Please pull the latest efi/core git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-core-2020-10-12
# HEAD: 4d0a4388ccdd9482fef6b26f879d0f6099143f80 Merge branch 'efi/urgent' into efi/core, to pick up fixes
EFI changes for v5.10:
- Preliminary RISC-V enablement - the bulk of it will arrive via the RISCV tree.
- Relax decompressed image placement rules for 32-bit ARM
- Add support for passing MOK certificate table contents via a config table
rather than a EFI variable.
- Add support for 18 bit DIMM row IDs in the CPER records.
- Work around broken Dell firmware that passes the entire Boot#### variable
contents as the command line
- Add definition of the EFI_MEMORY_CPU_CRYPTO memory attribute so we can
identify it in the memory map listings.
- Don't abort the boot on arm64 if the EFI RNG protocol is available but
returns with an error
- Replace slashes with exclamation marks in efivarfs file names
- Split efi-pstore from the deprecated efivars sysfs code, so we can
disable the latter on !x86.
- Misc fixes, cleanups and updates.
Thanks,
Ingo
------------------>
Alex Kluver (2):
edac,ghes,cper: Add Row Extension to Memory Error Record
cper,edac,efi: Memory Error Record: bank group/address and chip id
Ard Biesheuvel (13):
efi/libstub: arm32: Base FDT and initrd placement on image address
efi/libstub: Export efi_low_alloc_above() to other units
efi/libstub: arm32: Use low allocation for the uncompressed kernel
efi: Add definition of EFI_MEMORY_CPU_CRYPTO and ability to report it
efi/arm64: libstub: Deal gracefully with EFI_RNG_PROTOCOL failure
efi: mokvar-table: fix some issues in new code
efi: pstore: disentangle from deprecated efivars module
efi: pstore: move workqueue handling out of efivars
efi: efivars: un-export efivars_sysfs_init()
efi: gsmi: fix false dependency on CONFIG_EFI_VARS
efi: remove some false dependencies on CONFIG_EFI_VARS
efi: efivars: limit availability to X86 builds
efi: mokvar: add missing include of asm/early_ioremap.h
Arvind Sankar (2):
efi/libstub: Add efi_warn and *_once logging helpers
efi/x86: Add a quirk to support command line arguments on Dell EFI firmware
Atish Patra (2):
include: pe.h: Add RISC-V related PE definition
efi: Rename arm-init to efi-init common for all arch
Lenny Szubowicz (3):
efi: Support for MOK variable config table
integrity: Move import of MokListRT certs to a separate routine
integrity: Load certs from the EFI MOK config table
Michael Schaller (1):
efivarfs: Replace invalid slashes with exclamation marks in dentries.
Tian Tao (3):
efi/printf: remove unneeded semicolon
efi/libstub: Fix missing-prototypes in string.c
efi: Delete deprecated parameter comments
Documentation/arm/uefi.rst | 2 +-
arch/arm/include/asm/efi.h | 23 +-
arch/arm64/include/asm/efi.h | 5 +-
arch/x86/kernel/setup.c | 1 +
arch/x86/platform/efi/efi.c | 3 +
drivers/edac/ghes_edac.c | 17 +-
drivers/firmware/efi/Kconfig | 18 +-
drivers/firmware/efi/Makefile | 3 +-
drivers/firmware/efi/cper.c | 18 +-
drivers/firmware/efi/{arm-init.c => efi-init.c} | 1 +
drivers/firmware/efi/efi-pstore.c | 83 +++++-
drivers/firmware/efi/efi.c | 53 ++--
drivers/firmware/efi/efivars.c | 45 +--
drivers/firmware/efi/libstub/arm32-stub.c | 178 +++---------
drivers/firmware/efi/libstub/arm64-stub.c | 9 +-
drivers/firmware/efi/libstub/efi-stub-helper.c | 101 ++++++-
drivers/firmware/efi/libstub/efi-stub.c | 48 +---
drivers/firmware/efi/libstub/efistub.h | 61 +++-
drivers/firmware/efi/libstub/fdt.c | 4 +-
drivers/firmware/efi/libstub/file.c | 5 +-
drivers/firmware/efi/libstub/relocate.c | 4 +-
drivers/firmware/efi/libstub/string.c | 1 +
drivers/firmware/efi/libstub/vsprintf.c | 2 +-
drivers/firmware/efi/mokvar-table.c | 359 ++++++++++++++++++++++++
drivers/firmware/efi/vars.c | 22 --
drivers/firmware/google/Kconfig | 2 +-
drivers/firmware/google/gsmi.c | 8 +-
fs/efivarfs/super.c | 3 +
include/linux/cper.h | 24 +-
include/linux/efi.h | 46 ++-
include/linux/pe.h | 3 +
security/integrity/platform_certs/load_uefi.c | 85 ++++--
32 files changed, 871 insertions(+), 366 deletions(-)
rename drivers/firmware/efi/{arm-init.c => efi-init.c} (99%)
create mode 100644 drivers/firmware/efi/mokvar-table.c
next reply other threads:[~2020-10-12 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 15:21 Ingo Molnar [this message]
2020-10-12 21:25 ` [GIT PULL] EFI changes for v5.10 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-09-17 7:49 Ard Biesheuvel
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=20201012152119.GA3476595@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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 NNTP newsgroup(s).