From: Ard Biesheuvel <ard.biesheuvel@linaro.org> To: linux-efi@vger.kernel.org, Ingo Molnar <mingo@kernel.org>, Thomas Gleixner <tglx@linutronix.de> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>, linux-kernel@vger.kernel.org, Ben Dooks <ben.dooks@codethink.co.uk>, Dave Young <dyoung@redhat.com>, Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>, Jerry Snitselaar <jsnitsel@redhat.com>, linux-integrity@vger.kernel.org, Lukas Wunner <lukas@wunner.de>, Lyude Paul <lyude@redhat.com>, Matthew Garrett <mjg59@google.com>, Octavian Purdila <octavian.purdila@intel.com>, Peter Jones <pjones@redhat.com>, Scott Talbert <swt@techie.net> Subject: [GIT PULL 0/7] EFI fixes for v5.4 Date: Wed, 2 Oct 2019 18:58:57 +0200 [thread overview] Message-ID: <20191002165904.8819-1-ard.biesheuvel@linaro.org> (raw) The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent for you to fetch changes up to d45bb93ac68495a8c53126742b4d2223101cfb7f: efi/x86: do not clean dummy variable in kexec path (2019-10-02 18:44:23 +0200) ---------------------------------------------------------------- A couple of EFI fixes for v5.4: - a cosmetic fix for the byte order of PCI class codes in CPER error reports - bail early instead of pointlessly iterating over all EFI variables looking for the one containing a supplementary ACPI SSDT table if we never specified a variable name to begin with - some fixes for TPM event log parsing - fix kexec hangs on OVMF/x86 caused by attempts to delete a dummy variable which shouldn't even exist at that point. ---------------------------------------------------------------- Ard Biesheuvel (1): efivar/ssdt: don't iterate over EFI vars if no SSDT override was specified Ben Dooks (1): efi: make unexported efi_rci2_sysfs_init static Dave Young (1): efi/x86: do not clean dummy variable in kexec path Jerry Snitselaar (1): efi/tpm: only set efi_tpm_final_log_size after successful event log parsing Lukas Wunner (1): efi: cper: Fix endianness of PCIe class code Peter Jones (2): efi/tpm: Don't access event->count when it isn't mapped. efi/tpm: don't traverse an event log with no events arch/x86/platform/efi/efi.c | 3 --- drivers/firmware/efi/cper.c | 2 +- drivers/firmware/efi/efi.c | 3 +++ drivers/firmware/efi/rci2-table.c | 2 +- drivers/firmware/efi/tpm.c | 24 ++++++++++++++++++------ include/linux/tpm_eventlog.h | 16 ++++++++++++---- 6 files changed, 35 insertions(+), 15 deletions(-)
next reply other threads:[~2019-10-02 17:03 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-02 16:58 Ard Biesheuvel [this message] 2019-10-02 16:58 ` [PATCH 1/7] efi: cper: Fix endianness of PCIe class code Ard Biesheuvel 2019-10-07 14:49 ` [tip: efi/urgent] efi/cper: " tip-bot2 for Lukas Wunner 2019-10-02 16:58 ` [PATCH 2/7] efivar/ssdt: don't iterate over EFI vars if no SSDT override was specified Ard Biesheuvel 2019-10-07 14:49 ` [tip: efi/urgent] efivar/ssdt: Don't " tip-bot2 for Ard Biesheuvel 2019-10-02 16:59 ` [PATCH 3/7] efi/tpm: Don't access event->count when it isn't mapped Ard Biesheuvel 2019-10-07 14:49 ` [tip: efi/urgent] " tip-bot2 for Peter Jones 2019-10-02 16:59 ` [PATCH 4/7] efi/tpm: don't traverse an event log with no events Ard Biesheuvel 2019-10-07 14:49 ` [tip: efi/urgent] efi/tpm: Don't " tip-bot2 for Peter Jones 2019-10-02 16:59 ` [PATCH 5/7] efi/tpm: only set efi_tpm_final_log_size after successful event log parsing Ard Biesheuvel 2019-10-07 14:49 ` [tip: efi/urgent] efi/tpm: Only set 'efi_tpm_final_log_size' " tip-bot2 for Jerry Snitselaar 2019-10-02 16:59 ` [PATCH 6/7] efi: make unexported efi_rci2_sysfs_init static Ard Biesheuvel 2019-10-07 14:49 ` [tip: efi/urgent] efi: Make unexported efi_rci2_sysfs_init() static tip-bot2 for Ben Dooks 2019-10-02 16:59 ` [PATCH 7/7] efi/x86: do not clean dummy variable in kexec path Ard Biesheuvel 2019-10-07 14:49 ` [tip: efi/urgent] efi/x86: Do " tip-bot2 for Dave Young
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=20191002165904.8819-1-ard.biesheuvel@linaro.org \ --to=ard.biesheuvel@linaro.org \ --cc=ben.dooks@codethink.co.uk \ --cc=dyoung@redhat.com \ --cc=jarkko.sakkinen@linux.intel.com \ --cc=jsnitsel@redhat.com \ --cc=linux-efi@vger.kernel.org \ --cc=linux-integrity@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lukas@wunner.de \ --cc=lyude@redhat.com \ --cc=mingo@kernel.org \ --cc=mjg59@google.com \ --cc=octavian.purdila@intel.com \ --cc=pjones@redhat.com \ --cc=swt@techie.net \ --cc=tglx@linutronix.de \ --subject='Re: [GIT PULL 0/7] EFI fixes for v5.4' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.