On Fri, Feb 21, 2014 at 10:28:49AM +0000, David Vrabel wrote: > On 20/02/14 20:13, Greg Kroah-Hartman wrote: > > On Thu, Feb 20, 2014 at 10:51:24AM +0000, David Vrabel wrote: > >> These two changes fix important bugs with 32-bit Xen PV guests. > >> > >> 0160676bba69523e8b0ac83f306cce7d342ed7c8 (xen/p2m: check MFN is in range > >> before using the m2p table) > > > > Now applied. > > > >> 7cde9b27e7b3a2e09d647bb4f6d94e842698d2d5 (xen: Fix possible user space > >> selector corruption) > > > > I had to edit this by-hand to get it to apply, can you verify I got it right? > > I can't find where you put it. But if it looks like this, it's ok. You should have gotten an email about it. > --- a/arch/x86/xen/smp.c > +++ b/arch/x86/xen/smp.c > @@ -245,6 +245,15 @@ static void __init xen_smp_prepare_boot_cpu(void) > old memory can be recycled */ > make_lowmem_page_readwrite(xen_initial_gdt); > > +#ifdef CONFIG_X86_32 > + /* > + * Xen starts us with XEN_FLAT_RING1_DS, but linux code > + * expects __USER_DS > + */ > + loadsegment(ds, __USER_DS); > + loadsegment(es, __USER_DS); > +#endif > + > xen_filter_cpu_maps(); > xen_setup_vcpu_info_placement(); > } Yes, that was correct. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html