From: Linus Torvalds <torvalds@linux-foundation.org>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: Laura Abbott <labbott@redhat.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Waiman Long <waiman.long@hpe.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Borislav Petkov <bp@alien8.de>, "Theodore Ts'o" <tytso@mit.edu>,
Arnd Bergmann <arnd@arndb.de>,
Greg KH <gregkh@linuxfoundation.org>,
Scott J Norton <scott.norton@hpe.com>,
Douglas Hatch <doug.hatch@hpe.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"the arch/x86 maintainers" <x86@kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode
Date: Fri, 3 Feb 2017 08:35:22 -0800 [thread overview]
Message-ID: <CA+55aFyv+s4w0Fnqk7SM1V0L895nCXOwMcHLDfZdsh1+9aUh7g@mail.gmail.com> (raw)
In-Reply-To: <f8b36e38-c1f6-82f8-0ed9-0c934ace44ac@canonical.com>
On Fri, Feb 3, 2017 at 6:16 AM, Joseph Salisbury
<joseph.salisbury@canonical.com> wrote:
> On 02/02/2017 03:36 PM, Laura Abbott wrote:
>>
>> You might try https://marc.info/?l=linux-kernel&m=148553171703761
>> which fixed https://bugzilla.redhat.com/show_bug.cgi?id=1384238
>
> This patch resolves the bug for multiple users. Thanks again for the
> pointer, Laura and Ard!
.. and that patch should be in mainline now (and is marked for
stable), having gotten merged with the EFI fixes pull yesterday.
Linus
prev parent reply other threads:[~2017-02-03 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 20:17 [REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode Joseph Salisbury
2017-02-02 20:34 ` Ard Biesheuvel
2017-02-02 20:36 ` Laura Abbott
2017-02-02 20:49 ` Joseph Salisbury
2017-02-03 14:16 ` Joseph Salisbury
2017-02-03 16:35 ` Linus Torvalds [this message]
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=CA+55aFyv+s4w0Fnqk7SM1V0L895nCXOwMcHLDfZdsh1+9aUh7g@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--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=joseph.salisbury@canonical.com \
--cc=labbott@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=scott.norton@hpe.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=waiman.long@hpe.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).