From: Waiman Long <waiman.long@hpe.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
<linux-kernel@vger.kernel.org>, <linux-efi@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Borislav Petkov <bp@alien8.de>,
Douglas Hatch <doug.hatch@hpe.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Scott J Norton <scott.norton@hpe.com>, <stable@vger.kernel.org>
Subject: Re: [GIT PULL 0/2] EFI urgent fixes
Date: Tue, 20 Sep 2016 11:20:17 -0400 [thread overview]
Message-ID: <57E153B1.3040907@hpe.com> (raw)
In-Reply-To: <20160920144829.30873-1-matt@codeblueprint.co.uk>
On 09/20/2016 10:48 AM, Matt Fleming wrote:
> Folks, please pull the following two fixes that address the boot hang
> issue Waiman reported here,
>
> https://lkml.kernel.org/r/57DF56D4.50304@hpe.com
>
> The following changes since commit 3be7988674ab33565700a37b210f502563d932e6:
>
> Linux 4.8-rc7 (2016-09-18 17:27:41 -0700)
>
> 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 1297667083d5442aafe3e337b9413bf02b114edb:
>
> x86/efi: Only map RAM into EFI page tables if in mixed-mode (2016-09-20 14:53:04 +0100)
>
> ----------------------------------------------------------------
> * Fix a boot hang on large memory machines (multiple terabyte) caused
> by type conversion errors in the x86 pat code - Matt Fleming
>
> ----------------------------------------------------------------
> Matt Fleming (2):
> x86/mm/pat: Prevent hang during boot when mapping pages
> x86/efi: Only map RAM into EFI page tables if in mixed-mode
>
> arch/x86/mm/pageattr.c | 21 +++++++++++----------
> arch/x86/platform/efi/efi_64.c | 2 +-
> 2 files changed, 12 insertions(+), 11 deletions(-)
Are you also going to send these fixes to the 4.6 and 4.7 stable trees
as well?
Cheers,
Longman
next prev parent reply other threads:[~2016-09-20 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 14:48 [GIT PULL 0/2] EFI urgent fixes Matt Fleming
2016-09-20 14:48 ` [PATCH 1/2] x86/mm/pat: Prevent hang during boot when mapping pages Matt Fleming
2016-09-20 14:48 ` [PATCH 2/2] x86/efi: Only map RAM into EFI page tables if in mixed-mode Matt Fleming
2016-09-20 14:58 ` [GIT PULL 0/2] EFI urgent fixes Ingo Molnar
2016-09-20 15:20 ` Waiman Long [this message]
2016-09-20 15:27 ` Matt Fleming
-- strict thread matches above, loose matches on Subject: below --
2016-11-12 21:04 Matt Fleming
2016-08-11 10:41 Matt Fleming
2016-05-31 10:23 Matt Fleming
2016-06-06 10:02 ` Matt Fleming
2016-06-08 7:24 ` Ingo Molnar
2016-02-16 12:59 Matt Fleming
2016-02-16 15:47 ` Ingo Molnar
2015-09-25 22:02 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=57E153B1.3040907@hpe.com \
--to=waiman.long@hpe.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=doug.hatch@hpe.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=scott.norton@hpe.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).