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: Matt Fleming <matt@codeblueprint.co.uk>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
Dave Young <dyoung@redhat.com>, Omar Sandoval <osandov@fb.com>,
Peter Jones <pjones@redhat.com>,
stable@vger.kernel.org
Subject: [GIT PULL] EFI urgent fix
Date: Wed, 12 Apr 2017 16:27:18 +0100 [thread overview]
Message-ID: <20170412152719.9779-1-matt@codeblueprint.co.uk> (raw)
Folks, please pull the single below fix from Omar which fixes a kexec
boot regression.
I've based the pull on tip/efi/urgent since the EFI urgent queue
hasn't reached Linus' tree yet.
The following changes since commit 55d728a40d368ba80443be85c02e641fc9082a3f:
efi/fb: Avoid reconfiguration of BAR that covers the framebuffer (2017-04-05 12:25:53 +0200)
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 09ca0b10e8100a48aa94eb8649f4c6c904e5d196:
x86/efi: Don't try to reserve runtime regions (2017-04-12 16:17:20 +0100)
----------------------------------------------------------------
- Fix a crash on kexec boot introduced by the recent
efi_mem_reserve() code in the ESRT driver, which double-reserved
EFI runtime regions - Omar Sandoval
----------------------------------------------------------------
Omar Sandoval (1):
x86/efi: Don't try to reserve runtime regions
arch/x86/platform/efi/quirks.c | 4 ++++
1 file changed, 4 insertions(+)
next reply other threads:[~2017-04-12 15:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 15:27 Matt Fleming [this message]
2017-04-12 15:27 ` [PATCH] x86/efi: Don't try to reserve runtime regions Matt Fleming
2017-04-13 6:13 ` [tip:efi/urgent] " tip-bot for Omar Sandoval
-- strict thread matches above, loose matches on Subject: below --
2017-01-27 22:06 [GIT PULL] EFI urgent fix Matt Fleming
2016-05-13 20:34 Matt Fleming
2016-04-25 11:26 Matt Fleming
2016-04-25 15:29 ` Ingo Molnar
2016-04-01 19:03 Matt Fleming
2016-04-02 7:32 ` Ingo Molnar
2015-11-04 10:47 Matt Fleming
2015-11-04 10:50 ` Thomas Gleixner
2015-10-16 10:01 Matt Fleming
2015-10-16 10:04 ` Ingo Molnar
2015-10-12 14:13 Matt Fleming
2015-07-15 14:31 Matt Fleming
2015-07-21 7:53 ` Ingo Molnar
2015-06-11 12:47 Matt Fleming
2015-06-11 14:43 ` Ingo Molnar
2015-06-12 15:00 ` Matt Fleming
2015-03-27 19:18 Matt Fleming
2014-09-19 10:33 Matt Fleming
2014-09-19 10:50 ` Ingo Molnar
2014-08-06 9:46 Matt Fleming
2014-07-07 6:43 Matt Fleming
2014-06-20 9:00 Matt Fleming
2014-06-20 9:28 ` Catalin Marinas
2014-06-20 13:39 ` Leif Lindholm
2014-06-20 13:49 ` Matt Fleming
2014-06-20 14:19 ` Leif Lindholm
2014-06-25 20:42 ` Matt Fleming
2014-05-03 5:51 Matt Fleming
2014-05-04 18:21 ` Ingo Molnar
2014-03-04 23:47 Matt Fleming
2013-09-19 12:41 Matt Fleming
2013-09-20 7:53 ` Ingo Molnar
2013-06-21 9:56 Matt Fleming
2013-04-26 16:30 Matt Fleming
2013-04-26 16:40 ` Linus Torvalds
2013-04-26 16:48 ` 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=20170412152719.9779-1-matt@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=osandov@fb.com \
--cc=pjones@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.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).