public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: linmiaohe <linmiaohe@huawei.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
	"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
	"vkuznets@redhat.com" <vkuznets@redhat.com>,
	"wanpengli@tencent.com" <wanpengli@tencent.com>,
	"jmattson@google.com" <jmattson@google.com>,
	"joro@8bytes.org" <joro@8bytes.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"bp@alien8.de" <bp@alien8.de>, "hpa@zytor.com" <hpa@zytor.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH] KVM: X86: eliminate some meaningless code
Date: Mon, 24 Feb 2020 01:44:43 +0000	[thread overview]
Message-ID: <5ac7a51dbcc7408d87b14be75b41f1dc@huawei.com> (raw)

Sean Christopherson <sean.j.christopherson@intel.com> wrote:
> On Fri, Feb 21, 2020 at 10:05:26PM +0800, linmiaohe wrote:
>> From: Miaohe Lin <linmiaohe@huawei.com>
>> 
>> When kvm_vcpu_ioctl_get_cpuid2() fails, we set cpuid->nent to the 
>> value of
>> vcpu->arch.cpuid_nent. But this is in vain as cpuid->nent is not 
>> vcpu->copied to
>> userspace by copy_to_user() from call site. Get rid of this 
>> meaningless assignment and further cleanup the var r and out jump label.
>
>Ha, took me a while to see that.

Sorry about it. I'am not good at it. :(

>>
>> On the other hand, when kvm_vcpu_ioctl_get_cpuid2() succeeds, we do 
>>  			 vcpu->arch.cpuid_nent * sizeof(struct kvm_cpuid_entry2)))
>> -		goto out;
>> -	return 0;
>
>Hmm, so this ioctl() is straight up broken.  cpuid->nent should be updated on success so that userspace knows how many entries were retrieved, i.e.
>the code should look something like below, with kvm_arch_vcpu_ioctl() unchanged.
>
>I'm guessing no VMM actually uses this ioctl(), e.g. neither Qemu or CrosVM use it, which is why the broken behavior has gone unnoticed.  Don't suppose you'd want to write a selftest to hammer KVM_{SET,GET}_CPUID2?
>
>int kvm_vcpu_ioctl_get_cpuid2(struct kvm_vcpu *vcpu,
>                              struct kvm_cpuid2 *cpuid,
>                              struct kvm_cpuid_entry2 __user *entries) {
>        if (cpuid->nent < vcpu->arch.cpuid_nent)
>                return -E2BIG;
>
>        if (copy_to_user(entries, &vcpu->arch.cpuid_entries,
>                         vcpu->arch.cpuid_nent * sizeof(struct kvm_cpuid_entry2)))
>                return -EFAULT;
>
>	cpuid->nent = vcpu->arch.cpuid_nent;
>
>        return 0;
>}
>

I searched KVM_GET_CPUID2 from Qemu, it's not used. So maybe we could just drop KVM_GET_CPUID2 altogether as
suggested by Paolo. Thanks for your review.


             reply	other threads:[~2020-02-24  1:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24  1:44 linmiaohe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-24  1:54 [PATCH] KVM: X86: eliminate some meaningless code linmiaohe
2020-02-21 14:05 linmiaohe
2020-02-21 15:23 ` Sean Christopherson
2020-02-21 16:31   ` Paolo Bonzini

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=5ac7a51dbcc7408d87b14be75b41f1dc@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=sean.j.christopherson@intel.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    --cc=x86@kernel.org \
    /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