On Tue, 2017-02-07 at 06:52 +, Tian, Kevin wrote:
> > From: Sergey Dyasli [mailto:sergey.dya...@citrix.com]
> > Sent: Monday, February 06, 2017 10:58 PM
> >
> > There is an issue with the original __vmread() in nested vmx mode:
> > emulation of a guest's VMREAD with invalid arguments leads to
> From: Sergey Dyasli [mailto:sergey.dya...@citrix.com]
> Sent: Monday, February 06, 2017 10:58 PM
>
> There is an issue with the original __vmread() in nested vmx mode:
> emulation of a guest's VMREAD with invalid arguments leads to BUG().
>
> Fix this by using vmread_safe() and reporting any ki
There is an issue with the original __vmread() in nested vmx mode:
emulation of a guest's VMREAD with invalid arguments leads to BUG().
Fix this by using vmread_safe() and reporting any kind of VMfail back
to the guest.
A new safe versions of get_vvmcs() macro and related functions are
introduced