linux-kernel - Re: [RFC 05/12] KVM/VMX: Use the new host mapping API for mapping nested vmptr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALMp9eScXeCi6J4kuktdZmmOg2oDyyatpzOdVmUSso7F8FU+zA@mail.gmail.com>
Date:   Mon, 05 Feb 2018 22:15:01 +0000
From:   Jim Mattson <jmattson@...gle.com>
To:     KarimAllah Ahmed <karahmed@...zon.de>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        kvm list <kvm@...r.kernel.org>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Radim Krčmář <rkrcmar@...hat.com>
Subject: Re: [RFC 05/12] KVM/VMX: Use the new host mapping API for mapping
 nested vmptr

On Mon, Feb 5, 2018 at 10:49 AM KarimAllah Ahmed <karahmed@...zon.de> wrote:


> @@ -7410,19 +7410,17 @@ static int handle_vmon(struct kvm_vcpu *vcpu)
>                  return kvm_skip_emulated_instruction(vcpu);
>          }

> -       page = kvm_vcpu_gpa_to_page(vcpu, vmptr);
> -       if (is_error_page(page)) {
> +       if (!kvm_vcpu_gpa_to_host_mapping(vcpu, vmptr, &mapping, true)) {
>                  nested_vmx_failInvalid(vcpu);
>                  return kvm_skip_emulated_instruction(vcpu);
>          }
> -       if (*(u32 *)kmap(page) != VMCS12_REVISION) {
> -               kunmap(page);
> -               kvm_release_page_clean(page);
> +       if (*(u32 *)mapping.kaddr != VMCS12_REVISION) {
> +               kvm_release_host_mapping(&mapping, false);
>                  nested_vmx_failInvalid(vcpu);
>                  return kvm_skip_emulated_instruction(vcpu);
>          }
> -       kunmap(page);
> -       kvm_release_page_clean(page);
> +
> +       kvm_release_host_mapping(&mapping, false);

Why go through this explicit mapping/release dance? Why not just:

uint32_t revision;
...
if (kvm_read_guest(vcpu->kvm, vmptr, &revision, sizeof(revision)) ||
     revision != VMCS12_REVISION) {
         nested_vmx_failInvalid(vcpu);
         return kvm_skip_emulated_instruction(vcpu);
}