[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160312230225.GT15775@codeblueprint.co.uk>
Date: Sat, 12 Mar 2016 23:02:25 +0000
From: Matt Fleming <matt@...eblueprint.co.uk>
To: torvalds@...ux-foundation.org, dvlasenk@...hat.com, hpa@...or.com,
ard.biesheuvel@...aro.org, bp@...en8.de, luto@...capital.net,
amurzeau@...il.com, ben@...adent.org.uk, mjg59@...f.ucam.org,
tglx@...utronix.de, hertzog@...ian.org, mingo@...nel.org,
maarten.lankhorst@...onical.com, linux-kernel@...r.kernel.org,
brgerst@...il.com, rogershimizu@...il.com, peterz@...radead.org
Cc: linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/urgent] x86/efi: Fix boot crash by always mapping boot
service regions into new EFI page tables
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@...eblueprint.co.uk>
> AuthorDate: Fri, 11 Mar 2016 11:19:23 +0000
> Committer: Ingo Molnar <mingo@...nel.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.
It should be harmless to merge this patch before that, but the
references to separate EFI page tables don't make sense.
Powered by blists - more mailing lists