From: "Jan Beulich" Subject: Re: [Xen-devel] [PATCH] Solved the Xen PV/KASLR riddle Date: Fri, 29 Aug 2014 15:44:06 +0100 Message-ID: <5400ADD6020000780002F159@mail.emea.novell.com> References: <20140827204940.GA10556@laptop.dumpdata.com> <1409248903-19625-1-git-send-email-stefan.bader@canonical.com> <20140829140823.GF3609@laptop.dumpdata.com> <54008DDA.3040701@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <54008DDA.3040701@canonical.com> Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org To: Stefan Bader , Konrad Rzeszutek Wilk Cc: Kees Cook , David Vrabel , "xen-devel@lists.xensource.com" , Linux Kernel Mailing List List-Id: xen-devel@lists.xenproject.org >>> On 29.08.14 at 16:27, wrote: > Sure. Btw, someone also contacted me saying they have the same problem > without > changing the layout but having really big initrd (500M). While that feels > like > it should be impossible (if the kernel+initrd+xen stuff has to fix the 512M > kernel image size area then). But if it can happen, then surely it does > cause > mappings to be where the module space starts then. Since the initrd doesn't really need to be mapped into the (limited) virtual address space a pv guest starts with, we specifically got /* * Whether or not the guest can deal with being passed an initrd not * mapped through its initial page tables. */ #define XEN_ELFNOTE_MOD_START_PFN 16 to deal with that situation. The hypervisor side for Dom0 is in place, and the kernel side works in our (classic) kernels. Whether it got implemented for DomU meanwhile I don't know; I'm pretty certain pv-ops kernels don't support it so far. Jan