[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-changelog] [xen-unstable] x86: don't allow Dom0 to map MSI-X table writably
# HG changeset patch # User Jan Beulich <jbeulich@xxxxxxxx> # Date 1329303884 -3600 # Node ID 618cbd27bac06fe39b1c6f28ded6d4d7f444e7bd # Parent 0ba87b95e80bae059fe70b4b117dcc409f2471ef x86: don't allow Dom0 to map MSI-X table writably With the traditional qemu tree fixed to not use PROT_WRITE anymore in the mmap() call for this region, and with the upstream qemu tree not being capable of handling passthrough, yet, there's no need to treat Dom specially here anymore. This continues to leave unaddressed the case where PV guests map the MSI-X table page(s) before setting up the first MSI-X interrupt (see the original c/s 22182:68cc3c514a0a description for options). Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Keir Fraser <keir@xxxxxxx> --- diff -r 0ba87b95e80b -r 618cbd27bac0 xen/arch/x86/mm.c --- a/xen/arch/x86/mm.c Mon Feb 13 17:26:08 2012 +0000 +++ b/xen/arch/x86/mm.c Wed Feb 15 12:04:44 2012 +0100 @@ -869,7 +869,7 @@ return -EINVAL; } - if ( !(l1f & _PAGE_RW) || IS_PRIV(pg_owner) || + if ( !(l1f & _PAGE_RW) || !rangeset_contains_singleton(mmio_ro_ranges, mfn) ) return 0; dprintk(XENLOG_G_WARNING, _______________________________________________ Xen-changelog mailing list Xen-changelog@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-changelog
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |