From: Matt Fleming <matt@console-pimps.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Linux EFI <linux-efi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Lejun Zhu <lejun.zhu@intel.com>, Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] x86, efi: Fix 32-bit fallout
Date: Fri, 14 Feb 2014 09:22:23 +0000 [thread overview]
Message-ID: <20140214092223.GH20717@console-pimps.org> (raw)
In-Reply-To: <1392362664-26608-1-git-send-email-bp@alien8.de>
On Fri, 14 Feb, at 08:24:24AM, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
>
> We do not enable the new efi memmap on 32-bit and thus we need to run
> runtime_code_page_mkexec() unconditionally there. Fix that.
>
> Reported-and-tested-by: Lejun Zhu <lejun.zhu@intel.com>
> Cc: <stable@vger.kernel.org> # v3.14+
> Signed-off-by: Borislav Petkov <bp@suse.de>
Should this definitely be tagged for -stable? I'm not sure it makes
sense to backport your EFI memmap rototill, so this has only been broken
since v3.14-rc1.
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2014-02-14 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 7:24 [PATCH] x86, efi: Fix 32-bit fallout Borislav Petkov
2014-02-14 9:22 ` 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=20140214092223.GH20717@console-pimps.org \
--to=matt@console-pimps.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=lejun.zhu@intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.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).