On 12/06/18 16:38, Manuel Bouyer wrote: > On Tue, Jun 12, 2018 at 01:39:05PM +0200, Manuel Bouyer wrote: >> I applied this patch to 4.11rc4 (let's not change too much things at the >> same time) and rebooted my test host. Hopefully I'll have some data to report >> soon > Got the first panic (still from a i386 domU): > login: (XEN) d4v0 Hit #DB in Xen context: e008:ffff82d08036eb00 [overflow], > stk 0000:ffff8301bf117f78, dr6 ffff0ff0 > (XEN) d4v0 Hit #DB in Xen context: e008:ffff82d08036eb00 [overflow], stk > 0000:ffff8301bf117f78, dr6 ffff0ff0 > (XEN) d4v0 Hit #DB in Xen context: e008:ffff82d08036eb00 [overflow], stk > 0000:ffff8301bf117f78, dr6 ffff0ff0 > (XEN) d4v0 Hit #DB in Xen context: e008:ffff82d08036eb00 [overflow], stk > 0000:ffff8301bf117f78, dr6 ffff0ff0 > (XEN) d4v0 Hit #DB in Xen context: e008:ffff82d08036eb00 [overflow], stk > 0000:ffff8301bf117f78, dr6 ffff0ff0 > (XEN) d4v2 Hit #DB in Xen context: e008:ffff82d08036eb00 [overflow], stk > 0000:ffff8301bf077f78, dr6 ffff0ff0
I presume you're running a XSA-263 (MovSS) exploit in testing? ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
