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,
Heinrich Schuchardt <xypron.glpk@gmx.de>, Qian Cai <cai@gmx.us>
Subject: [GIT PULL 0/2] Final EFI fixes for v4.20
Date: Mon, 17 Dec 2018 19:02:12 +0100 [thread overview]
Message-ID: <20181217180214.9436-1-ard.biesheuvel@linaro.org> (raw)
The following changes since commit 7566ec393f4161572ba6f11ad5171fd5d59b0fbd:
Linux 4.20-rc7 (2018-12-16 15:46:55 -0800)
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 7b671e6a4917594a4e9ffd64111b8ac2e0323837:
efi: efi_guid_t must be 64-bit aligned (2018-12-17 10:42:26 +0100)
Note that applying Qian's patch will result in a conflict with the EFI
changes queued for the next window - the solution is to simply drop the
kmemleak_ignore() call since it is not required for page based
allocations.
----------------------------------------------------------------
Final EFI fixes for v4.20:
- prevent false positives from kmemleak for persistent memory reservations
- use the correct alignment for EFI GUIDs, preventing potential crashes in
firmware calls on 32-bit ARM
----------------------------------------------------------------
Heinrich Schuchardt (1):
efi: efi_guid_t must be 64-bit aligned
Qian Cai (1):
efi: let kmemleak ignore false positives
drivers/firmware/efi/efi.c | 3 +++
include/linux/efi.h | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
next reply other threads:[~2018-12-17 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 18:02 Ard Biesheuvel [this message]
2018-12-17 18:02 ` [PATCH 1/2] efi: let kmemleak ignore false positives Ard Biesheuvel
2018-12-17 18:02 ` [PATCH 2/2] efi: efi_guid_t must be 64-bit aligned Ard Biesheuvel
[not found] ` <20181218204116.6D58A2184C@mail.kernel.org>
2018-12-19 10:07 ` Ard Biesheuvel
2018-12-19 14:06 ` Sasha Levin
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=20181217180214.9436-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=cai@gmx.us \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=xypron.glpk@gmx.de \
/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).