On Tue, Feb 04, 2020 at 08:29:38PM +0000, Andrew Cooper wrote: > It turns out that a bug (since forever) in Xen causes XSAVE records to have > non-architectural behaviour on xsave-capable hardware, when a PV guest has not > touched the state. > > In such a case, the data record returned from Xen is 2*uint64_t, both claiming > the (illegitimate) state of %xcr0 and %xcr0_accum being 0. > > Adjust the bound in handle_x86_pv_vcpu_blob() to cope with this. > > Fixes: 2a62c22715b "libxc/restore: Fix data auditing in > handle_x86_pv_vcpu_blob()" > Reported-by: Igor Druzhinin <igor.druzhi...@citrix.com> > Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
Acked-by: Wei Liu <w...@xen.org> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
