From: Ingo Molnar <mingo@kernel.org>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: torvalds@linux-foundation.org, dvlasenk@redhat.com,
hpa@zytor.com, ard.biesheuvel@linaro.org, bp@alien8.de,
luto@amacapital.net, amurzeau@gmail.com, ben@decadent.org.uk,
mjg59@srcf.ucam.org, tglx@linutronix.de, hertzog@debian.org,
maarten.lankhorst@canonical.com, linux-kernel@vger.kernel.org,
brgerst@gmail.com, rogershimizu@gmail.com, peterz@infradead.org,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86/efi: Fix boot crash by always mapping boot service regions into new EFI page tables
Date: Sun, 13 Mar 2016 18:56:11 +0100 [thread overview]
Message-ID: <20160313175611.GA24113@gmail.com> (raw)
In-Reply-To: <20160312230225.GT15775@codeblueprint.co.uk>
* Matt Fleming <matt@codeblueprint.co.uk> wrote:
> On Sat, 12 Mar, at 10:57:39AM, tip-bot for Matt Fleming wrote:
> > Commit-ID: 452308de61056a539352a9306c46716d7af8a1f1
> > Gitweb: http://git.kernel.org/tip/452308de61056a539352a9306c46716d7af8a1f1
> > Author: Matt Fleming <matt@codeblueprint.co.uk>
> > AuthorDate: Fri, 11 Mar 2016 11:19:23 +0000
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitDate: Sat, 12 Mar 2016 16:57:45 +0100
> >
> > x86/efi: Fix boot crash by always mapping boot service regions into new EFI page tables
>
> Ingo, I see you picked this up for x86/urgent, but note that the bug
> isn't actually triggerable until the stuff in tip/efi/core gets
> merged. I'd suggest sticking this patch in tip/efi/core also.
Oh well ... too late for that, it's now upstream.
> It should be harmless to merge this patch before that, but the
> references to separate EFI page tables don't make sense.
Yeah, indeed. It's my bad: we merged the EFI-pagetables code back in
November and I forgot that we skipped its upstream merge twice ...
Thanks,
Ingo
next prev parent reply other threads:[~2016-03-13 17:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 11:19 [GIT PULL] EFI urgent fix for v4.6 queue Matt Fleming
2016-03-11 11:19 ` [PATCH] x86/efi: Always map boot service regions into new EFI page tables Matt Fleming
2016-03-12 18:57 ` [tip:x86/urgent] x86/efi: Fix boot crash by always mapping " tip-bot for Matt Fleming
2016-03-12 23:02 ` Matt Fleming
2016-03-13 17:56 ` Ingo Molnar [this message]
2016-03-13 17:09 ` [PATCH] x86/efi: Always map " Scott Ashcroft
2016-03-13 21:58 ` Matt Fleming
2016-03-13 23:07 ` Matt Fleming
2016-03-13 23:44 ` Scott Ashcroft
2016-03-14 1:09 ` Scott Ashcroft
2016-03-14 10:30 ` Ingo Molnar
2016-03-14 11:35 ` Matt Fleming
2016-03-14 12:05 ` Ingo Molnar
2016-03-14 14:27 ` Matt Fleming
2016-03-14 16:47 ` Ingo Molnar
2016-03-15 15:54 ` Matt Fleming
2016-03-15 16:05 ` Borislav Petkov
2016-03-15 16:25 ` Julia Lawall
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=20160313175611.GA24113@gmail.com \
--to=mingo@kernel.org \
--cc=amurzeau@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ben@decadent.org.uk \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hertzog@debian.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=maarten.lankhorst@canonical.com \
--cc=matt@codeblueprint.co.uk \
--cc=mjg59@srcf.ucam.org \
--cc=peterz@infradead.org \
--cc=rogershimizu@gmail.com \
--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