From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH 1/8] x86, kaslr: get kaslr_enabled back correctly Date: Mon, 2 Mar 2015 15:53:13 +0100 Message-ID: <20150302145313.GC17532@pd.tnic> References: <20150301094557.GA7748@pd.tnic> <20150301152351.GA17391@gmail.com> <20150301194904.GC7748@pd.tnic> <20150301202938.GD7748@pd.tnic> <20150302085654.GA17532@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-pci-owner@vger.kernel.org To: Yinghai Lu Cc: Ingo Molnar , Jiri Kosina , Kees Cook , Matt Fleming , Thomas Gleixner , "H. Peter Anvin" , Ingo Molnar , Bjorn Helgaas , Linus Torvalds , Linux Kernel Mailing List , "linux-efi@vger.kernel.org" , "linux-pci@vger.kernel.org" List-Id: linux-efi@vger.kernel.org On Mon, Mar 02, 2015 at 03:04:30AM -0800, Yinghai Lu wrote: > We can not assume that range is safe to use. > > Please check attach one that should fix the problem really. Well, it seems to work here but it still doesn't look reliable enough to me. And this addon_zo thing of arbitrary 256K is strange. What we should do instead and IMHO is have a special setup_data section located right above .text where struct setup_data things are put in so that they never get overwritten. This should be the cleanest IMHO. It is hpa's call in the end of the day anyway. Thanks. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --