From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH] x86/efi: Map EFI memmap entries in-order at runtime Date: Thu, 17 Sep 2015 10:05:12 +0200 Message-ID: <20150917080511.GG12379@nazgul.tnic> References: <1441372447-23439-1-git-send-email-matt@codeblueprint.co.uk> <20150907040752.GW13182@linux-rxt1.site> <20150908204147.GC2854@codeblueprint.co.uk> <20150909003307.GJ2266@linux-rxt1.site> <20150909112123.GB4973@codeblueprint.co.uk> <20150916100820.GA7077@nazgul.tnic> <20150916132822.GB9198@nazgul.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org To: Ard Biesheuvel Cc: Matt Fleming , joeyli , "linux-efi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "x86@kernel.org" , Matt Fleming , Leif Lindholm , Peter Jones , James Bottomley , Matthew Garrett , "H. Peter Anvin" , Dave Young , "stable@vger.kernel.org" List-Id: linux-efi@vger.kernel.org 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. --=20 Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imend=C3=B6rffer, Jane Smithard, Graham Nort= on, HRB 21284 (AG N=C3=BCrnberg) --