diff options
author | Liran Alon <liran.alon@oracle.com> | 2019-07-15 18:47:44 +0300 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2019-07-15 20:40:58 +0200 |
commit | 6694e48012826351036fd10fc506ca880023e25f (patch) | |
tree | bc5d3faa50f4a6df7f454ffa9c2b50c9191e733f /arch/powerpc/boot/Makefile | |
parent | 0d88800d547211ce07be3551c812d404cf2be3a8 (diff) | |
download | linux-6694e48012826351036fd10fc506ca880023e25f.tar.gz linux-6694e48012826351036fd10fc506ca880023e25f.tar.bz2 linux-6694e48012826351036fd10fc506ca880023e25f.zip |
KVM: nVMX: Ignore segment base for VMX memory operand when segment not FS or GS
As reported by Maxime at
https://bugzilla.kernel.org/show_bug.cgi?id=204175:
In vmx/nested.c::get_vmx_mem_address(), when the guest runs in long mode,
the base address of the memory operand is computed with a simple:
*ret = s.base + off;
This is incorrect, the base applies only to FS and GS, not to the others.
Because of that, if the guest uses a VMX instruction based on DS and has
a DS.base that is non-zero, KVM wrongfully adds the base to the
resulting address.
Reported-by: Maxime Villard <max@m00nbsd.net>
Reviewed-by: Joao Martins <joao.m.martins@oracle.com>
Signed-off-by: Liran Alon <liran.alon@oracle.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/powerpc/boot/Makefile')
0 files changed, 0 insertions, 0 deletions