From: Matt Fleming <matt@codeblueprint.co.uk>
To: Jiri Kosina <jikos@kernel.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Waiman Long <waiman.long@hpe.com>, Borislav Petkov <bp@suse.de>,
Laura Abbott <labbott@redhat.com>,
Vojtech Pavlik <vojtech@ucw.cz>, Hanka Pavlikova <hanka@ucw.cz>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: [PATCH v2] x86/efi: always map first physical page into EFI pagetables
Date: Fri, 27 Jan 2017 16:23:15 +0000 [thread overview]
Message-ID: <20170127162315.GG31613@codeblueprint.co.uk> (raw)
In-Reply-To: <alpine.LSU.2.20.1701271638240.25515@cbobk.fhfr.pm>
On Fri, 27 Jan, at 04:39:59PM, Jiri Kosina wrote:
> From: Jiri Kosina <jkosina@suse.cz>
>
> Commit 129766708 ("x86/efi: Only map RAM into EFI page tables if in
> mixed-mode") stopped creating 1:1 mapping for all RAM in case of running
> in native 64bit mode.
>
> It turns out though that there are 64bit EFI implementations in the wild
> (this particular problem has been reported on Lenovo Yoga 710-11IKB) which
> still make use of first physical page for their own private use even
> though they explicitly mark it EFI_CONVENTIONAL_MEMORY in the memory map.
>
> In case there is no mapping for this particular frame in EFI pagetables,
> as soon as firmware tries to make use of it, triple fault occurs and the
> system reboots (in case of Yoga 710-11IKB this is very early during boot).
>
> Fix that by always mapping the first page of physical memory into EFI
> pagetables. We're on a safe side, as trim_bios_range() will reserve the
> first page and isolate it away from memory allocators anyway.
>
> Note: just reverting 129766708 is not enough on v4.9-rc1+ to fix the
> regression on affected hardware, as commit ab72a27da ("x86/efi:
> Consolidate region mapping logic") later made the first physical frame not
> to be mapped anyway.
>
> Fixes: 129766708 ("x86/efi: Only map RAM into EFI page tables if in mixed-mode")
> Cc: stable@kernel.org # v4.8+
> Cc: Waiman Long <waiman.long@hpe.com>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: Laura Abbott <labbott@redhat.com>
> Cc: Vojtech Pavlik <vojtech@ucw.cz>
> Reported-by: Hanka Pavlikova <hanka@ucw.cz>
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> ---
Thanks Jiri. Queued for v4.10-rc6.
prev parent reply other threads:[~2017-01-27 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LSU.2.20.1701252048550.25515@cbobk.fhfr.pm>
2017-01-25 20:31 ` [PATCH] x86/efi: always map first physical page into EFI pagetables Jiri Kosina
2017-01-25 20:36 ` Borislav Petkov
2017-01-27 15:12 ` Matt Fleming
2017-01-27 15:39 ` [PATCH v2] " Jiri Kosina
2017-01-27 16:23 ` Matt Fleming [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=20170127162315.GG31613@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@suse.de \
--cc=hanka@ucw.cz \
--cc=jikos@kernel.org \
--cc=labbott@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@ucw.cz \
--cc=waiman.long@hpe.com \
/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).