From: Ard Biesheuvel <ardb@kernel.org>
To: linux-efi@vger.kernel.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] EFI fixes for v5.8
Date: Thu, 18 Jun 2020 15:37:14 +0200 [thread overview]
Message-ID: <20200618133714.1227453-1-ardb@kernel.org> (raw)
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent-for-v5.8-rc1
for you to fetch changes up to 2a55280a3675203496d302463b941834228b9875:
efi/libstub: arm: Print CPU boot mode and MMU state at boot (2020-06-17 15:29:11 +0200)
----------------------------------------------------------------
EFI fixes for v5.8-rc1:
- Fix build regression on v4.8 and older
- Robustness fix for TPM log parsing code
- kobject refcount fix for the ESRT parsing code
- Two efivarfs fixes to make it behave more like an ordinary file system
- Style fixup for zero length arrays
- Fix a regression in path separator handling in the initrd loader
- Fix a missing prototype warning
- Add some kerneldoc headers for newly introduced stub routines
- Allow support for SSDT overrides via EFI variables to be disabled
- Report CPU mode and MMU state upon entry for 32-bit ARM
- Use the correct stack pointer alignment when entering from mixed mode
----------------------------------------------------------------
Ard Biesheuvel (3):
efi/libstub: Fix missing-prototype warning for skip_spaces()
efi/libstub: arm: Omit arch specific config table matching array on arm64
efi/libstub: arm: Print CPU boot mode and MMU state at boot
Arvind Sankar (2):
efi/x86: Fix build with gcc 4
efi/x86: Setup stack correctly for efi_pe_entry
Fabian Vogt (1):
efi/tpm: Verify event log header before parsing
Gustavo A. R. Silva (1):
efi: Replace zero-length array and use struct_size() helper
Heinrich Schuchardt (1):
efi/libstub: Descriptions for stub helper functions
Peter Jones (1):
efi: Make it possible to disable efivar_ssdt entirely
Philipp Fent (1):
efi/libstub: Fix path separator regression
Qiushi Wu (1):
efi/esrt: Fix reference count leak in esre_create_sysfs_entry.
Tony Luck (2):
efivarfs: Update inode modification time for successful writes
efivarfs: Don't return -EINTR when rate-limiting reads
arch/arm/include/asm/efi.h | 7 +++
arch/x86/boot/compressed/head_64.S | 11 +++-
drivers/firmware/efi/Kconfig | 11 ++++
drivers/firmware/efi/arm-init.c | 40 +++++++++++--
drivers/firmware/efi/efi.c | 5 +-
drivers/firmware/efi/esrt.c | 2 +-
drivers/firmware/efi/libstub/Makefile | 3 +-
drivers/firmware/efi/libstub/arm32-stub.c | 54 +++++++++++++++++-
drivers/firmware/efi/libstub/efi-stub-helper.c | 78 ++++++++++++++++++++++----
drivers/firmware/efi/libstub/efi-stub.c | 3 +
drivers/firmware/efi/libstub/efistub.h | 12 +++-
drivers/firmware/efi/libstub/file.c | 16 ++++--
drivers/firmware/efi/libstub/skip_spaces.c | 1 +
fs/efivarfs/file.c | 7 +--
include/linux/efi.h | 8 +--
include/linux/tpm_eventlog.h | 14 ++++-
16 files changed, 235 insertions(+), 37 deletions(-)
reply other threads:[~2020-06-18 13:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200618133714.1227453-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®