From: Borislav Petkov <bp@suse.de>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Matt Fleming <matt@codeblueprint.co.uk>, joeyli <jlee@suse.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
Peter Jones <pjones@redhat.com>,
James Bottomley <JBottomley@odin.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"H. Peter Anvin" <hpa@zytor.com>, Dave Young <dyoung@redhat.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] x86/efi: Map EFI memmap entries in-order at runtime
Date: Thu, 17 Sep 2015 10:05:12 +0200 [thread overview]
Message-ID: <20150917080511.GG12379@nazgul.tnic> (raw)
In-Reply-To: <CAKv+Gu84SJiJH-orFBk-mW6CA7XA0yOiU7DhLzWVTAg=u-yMOg@mail.gmail.com>
On Wed, Sep 16, 2015 at 03:38:45PM +0200, Ard Biesheuvel wrote:
> That is a can of worms I'd rather keep closed, if you don't mind ...
Same here.
> But in general, since we are already violating the PE/COFF spec by
> relocating each runtime image once, then invoke its entry point, then
> fire an event which it should catch to manually update its pointers,
> and then relocate it again into the OS VA space.
Yeah, I vaguely remember at the time hpa proposing an EFI-specific
page fault handler or so. I guess we should consider such or similar
technique as it should be most flexible to deal with such screwups. And
with whatever funky fw stuff comes our way in the future...
Thanks.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2015-09-17 8:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 13:14 Matt Fleming
2015-09-04 13:24 ` Ard Biesheuvel
2015-09-04 18:23 ` Matt Fleming
2015-09-04 18:53 ` Ard Biesheuvel
2015-09-06 14:06 ` Ard Biesheuvel
2015-09-08 13:16 ` Matt Fleming
2015-09-08 13:21 ` Ard Biesheuvel
2015-09-08 20:37 ` Matt Fleming
2015-09-09 7:37 ` Ard Biesheuvel
2015-09-09 9:58 ` Matt Fleming
2015-09-09 9:59 ` Ard Biesheuvel
2015-09-07 4:07 ` joeyli
2015-09-08 20:41 ` Matt Fleming
2015-09-09 0:33 ` joeyli
2015-09-09 11:21 ` Matt Fleming
2015-09-10 3:38 ` joeyli
2015-09-16 10:08 ` Borislav Petkov
2015-09-16 11:25 ` Ard Biesheuvel
2015-09-16 13:28 ` Borislav Petkov
2015-09-16 13:38 ` Ard Biesheuvel
2015-09-17 8:05 ` Borislav Petkov [this message]
2015-09-16 13:37 ` James Bottomley
2015-09-16 14:07 ` Ard Biesheuvel
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=20150917080511.GG12379@nazgul.tnic \
--to=bp@suse.de \
--cc=JBottomley@odin.com \
--cc=ard.biesheuvel@linaro.org \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=jlee@suse.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@codeblueprint.co.uk \
--cc=mjg59@srcf.ucam.org \
--cc=pjones@redhat.com \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®