From: Matt Fleming <matt@codeblueprint.co.uk>
To: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>,
Yinghai Lu <yinghai@kernel.org>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] EFI urgent fixes
Date: Mon, 2 Mar 2015 12:51:04 +0000 [thread overview]
Message-ID: <20150302125104.GC24476@codeblueprint.co.uk> (raw)
Folks, please pull the following urgent changes.
The following changes since commit 43a9f69692b232d1c64c913a27507eb14a1c47fd:
Revert "efi/libstub: Call get_memory_map() to obtain map and desc sizes" (2015-02-18 11:38:13 +0000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-urgent
for you to fetch changes up to 6d9ff473317245e3e5cd9922b4520411c2296388:
firmware: dmi_scan: Fix dmi_len type (2015-02-24 18:54:17 +0000)
----------------------------------------------------------------
* Fix regression in DMI sysfs code for handling "End of Table" entry
and a type bug that could lead to integer overflow - Ivan Khoronzhuk
* Fix boundary checking in efi_high_alloc() which can lead to memory
corruption in the EFI boot stubs - Yinghai Lu
----------------------------------------------------------------
Ivan Khoronzhuk (2):
firmware: dmi_scan: Fix dmi scan to handle "End of Table" structure
firmware: dmi_scan: Fix dmi_len type
Yinghai Lu (1):
efi/libstub: Fix boundary checking in efi_high_alloc()
drivers/firmware/dmi_scan.c | 17 +++++++++--------
drivers/firmware/efi/libstub/efi-stub-helper.c | 8 ++++----
2 files changed, 13 insertions(+), 12 deletions(-)
--
Matt Fleming, Intel Open Source Technology Center
next reply other threads:[~2015-03-02 12:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 12:51 Matt Fleming [this message]
2015-03-02 13:24 ` [GIT PULL] EFI urgent fixes Ingo Molnar
2015-03-02 13:35 ` Matt Fleming
-- strict thread matches above, loose matches on Subject: below --
2015-07-30 21:06 Matt Fleming
2015-07-31 7:56 ` Ingo Molnar
2015-05-05 16:27 Matt Fleming
2015-05-06 6:31 ` Ingo Molnar
2015-02-18 11:55 Matt Fleming
2015-02-18 13:43 ` Ingo Molnar
2015-02-18 16:36 ` Ard Biesheuvel
2015-02-18 16:57 ` Ingo Molnar
2014-09-25 7:31 Matt Fleming
2014-09-25 14:41 ` Ingo Molnar
2014-09-25 14:44 ` Matt Fleming
2014-09-26 11:27 ` Paul Bolle
2014-09-26 11:35 ` Ingo Molnar
2014-09-26 12:24 ` Matt Fleming
2014-09-27 5:49 ` Ingo Molnar
2014-09-26 11:44 ` Matt Fleming
2014-09-26 11:59 ` Paul Bolle
2014-09-26 12:34 ` Matt Fleming
2014-09-26 12:55 ` Paul Bolle
2014-09-27 8:04 ` Valentin Rothberg
2014-09-27 9:59 ` Paul Bolle
2014-09-08 21:55 Matt Fleming
2014-09-09 5:07 ` Ingo Molnar
2014-09-09 7:07 ` Matt Fleming
2014-09-09 14:55 ` Ingo Molnar
2014-08-22 7:52 Matt Fleming
2014-08-22 8:15 ` Ingo Molnar
2014-07-14 12:54 Matt Fleming
2014-06-27 14:51 Matt Fleming
2014-06-04 16:53 Matt Fleming
2014-04-11 7:16 Matt Fleming
2014-04-11 8:27 ` Ingo Molnar
2014-02-14 13:08 Matt Fleming
2013-11-29 12:09 Matt Fleming
2013-07-11 11:16 Matt Fleming
2013-06-07 11:50 Matt Fleming
2013-06-10 21:36 ` Matt Fleming
2013-05-17 10:18 Matt Fleming
2013-04-25 8:49 Matt Fleming
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=20150302125104.GC24476@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=hpa@zytor.com \
--cc=ivan.khoronzhuk@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=yinghai@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