From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Dongjie Zou <zoudongjie@huawei.com>
Subject: Re: [PATCH v2 3/4] KVM: selftests: Manage CPUID array in Hyper-V CPUID test's core helper
Date: Mon, 20 Jan 2025 15:20:50 +0100 [thread overview]
Message-ID: <875xm98t31.fsf@redhat.com> (raw)
In-Reply-To: <20250118003454.2619573-4-seanjc@google.com>
Sean Christopherson <seanjc@google.com> writes:
> Allocate, get, and free the CPUID array in the Hyper-V CPUID test in the
> test's core helper, instead of copy+pasting code at each call site. In
> addition to deduplicating a small amount of code, restricting visibility
> of the array to a single invocation of the core test prevents "leaking" an
> array across test cases. Passing in @vcpu to the helper will also allow
> pivoting on VM-scoped information without needing to pass more booleans,
> e.g. to conditionally assert on features that require an in-kernel APIC.
>
> To avoid use-after-free bugs due to overzealous and careless developers,
> opportunstically add a comment to explain that the system-scoped helper
> caches the Hyper-V CPUID entries, i.e. that the caller is not responsible
> for freeing the memory.
>
> Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> .../selftests/kvm/x86_64/hyperv_cpuid.c | 30 +++++++++++--------
> 1 file changed, 17 insertions(+), 13 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c b/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c
> index 9a0fcc713350..3188749ec6e1 100644
> --- a/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c
> +++ b/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c
> @@ -41,13 +41,18 @@ static bool smt_possible(void)
> return res;
> }
>
> -static void test_hv_cpuid(const struct kvm_cpuid2 *hv_cpuid_entries,
> - bool evmcs_expected)
> +static void test_hv_cpuid(struct kvm_vcpu *vcpu, bool evmcs_expected)
> {
> + const struct kvm_cpuid2 *hv_cpuid_entries;
> int i;
> int nent_expected = 10;
> u32 test_val;
>
> + if (vcpu)
> + hv_cpuid_entries = vcpu_get_supported_hv_cpuid(vcpu);
> + else
> + hv_cpuid_entries = kvm_get_supported_hv_cpuid();
> +
> TEST_ASSERT(hv_cpuid_entries->nent == nent_expected,
> "KVM_GET_SUPPORTED_HV_CPUID should return %d entries"
> " (returned %d)",
> @@ -109,6 +114,13 @@ static void test_hv_cpuid(const struct kvm_cpuid2 *hv_cpuid_entries,
> * entry->edx);
> */
> }
> +
> + /*
> + * Note, the CPUID array returned by the system-scoped helper is a one-
> + * time allocation, i.e. must not be freed.
> + */
> + if (vcpu)
> + free((void *)hv_cpuid_entries);
> }
>
> static void test_hv_cpuid_e2big(struct kvm_vm *vm, struct kvm_vcpu *vcpu)
> @@ -129,7 +141,6 @@ static void test_hv_cpuid_e2big(struct kvm_vm *vm, struct kvm_vcpu *vcpu)
> int main(int argc, char *argv[])
> {
> struct kvm_vm *vm;
> - const struct kvm_cpuid2 *hv_cpuid_entries;
> struct kvm_vcpu *vcpu;
>
> TEST_REQUIRE(kvm_has_cap(KVM_CAP_HYPERV_CPUID));
> @@ -138,10 +149,7 @@ int main(int argc, char *argv[])
>
> /* Test vCPU ioctl version */
> test_hv_cpuid_e2big(vm, vcpu);
> -
> - hv_cpuid_entries = vcpu_get_supported_hv_cpuid(vcpu);
> - test_hv_cpuid(hv_cpuid_entries, false);
> - free((void *)hv_cpuid_entries);
> + test_hv_cpuid(vcpu, false);
>
> if (!kvm_cpu_has(X86_FEATURE_VMX) ||
> !kvm_has_cap(KVM_CAP_HYPERV_ENLIGHTENED_VMCS)) {
> @@ -149,9 +157,7 @@ int main(int argc, char *argv[])
> goto do_sys;
> }
> vcpu_enable_evmcs(vcpu);
> - hv_cpuid_entries = vcpu_get_supported_hv_cpuid(vcpu);
> - test_hv_cpuid(hv_cpuid_entries, true);
> - free((void *)hv_cpuid_entries);
> + test_hv_cpuid(vcpu, true);
>
> do_sys:
> /* Test system ioctl version */
> @@ -161,9 +167,7 @@ int main(int argc, char *argv[])
> }
>
> test_hv_cpuid_e2big(vm, NULL);
> -
> - hv_cpuid_entries = kvm_get_supported_hv_cpuid();
> - test_hv_cpuid(hv_cpuid_entries, kvm_cpu_has(X86_FEATURE_VMX));
> + test_hv_cpuid(NULL, kvm_cpu_has(X86_FEATURE_VMX));
>
> out:
> kvm_vm_free(vm);
Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
--
Vitaly
next prev parent reply other threads:[~2025-01-20 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 0:34 [PATCH v2 0/4] KVM: x86: Hyper-V SEND_IPI fix and partial testcase Sean Christopherson
2025-01-18 0:34 ` [PATCH v2 1/4] KVM: x86: Reject Hyper-V's SEND_IPI hypercalls if local APIC isn't in-kernel Sean Christopherson
2025-01-18 0:34 ` [PATCH v2 2/4] KVM: selftests: Mark test_hv_cpuid_e2big() static in Hyper-V CPUID test Sean Christopherson
2025-01-18 0:34 ` [PATCH v2 3/4] KVM: selftests: Manage CPUID array in Hyper-V CPUID test's core helper Sean Christopherson
2025-01-20 14:20 ` Vitaly Kuznetsov [this message]
2025-01-18 0:34 ` [PATCH v2 4/4] KVM: selftests: Add CPUID tests for Hyper-V features that need in-kernel APIC Sean Christopherson
2025-01-20 14:20 ` Vitaly Kuznetsov
2025-01-21 16:00 ` Sean Christopherson
2025-01-21 16:29 ` Vitaly Kuznetsov
2025-02-15 0:50 ` [PATCH v2 0/4] KVM: x86: Hyper-V SEND_IPI fix and partial testcase Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xm98t31.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=zoudongjie@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).