From: Sean Christopherson <seanjc@google.com>
To: Valeriy Vdovin <valeriy.vdovin@virtuozzo.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
linux-kernel@vger.kernel.org, Denis Lunev <den@openvz.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Shuah Khan <shuah@kernel.org>,
Aaron Lewis <aaronlewis@google.com>,
Alexander Graf <graf@amazon.com>,
Like Xu <like.xu@linux.intel.com>,
Oliver Upton <oupton@google.com>,
Andrew Jones <drjones@redhat.com>,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Fix KVM_GET_CPUID2 ioctl to return cpuid entries count
Date: Wed, 28 Apr 2021 14:58:59 +0000 [thread overview]
Message-ID: <YIl4M/GgaYvwNuXv@google.com> (raw)
In-Reply-To: <20210428134657.GA515794@dhcp-172-16-24-191.sw.ru>
On Wed, Apr 28, 2021, Valeriy Vdovin wrote:
> On Wed, Apr 28, 2021 at 02:38:57PM +0200, Vitaly Kuznetsov wrote:
> > Valeriy Vdovin <valeriy.vdovin@virtuozzo.com> writes:
> >
> > > KVM_GET_CPUID2 kvm ioctl is not very well documented, but the way it is
> > > implemented in function kvm_vcpu_ioctl_get_cpuid2 suggests that even at
> > > error path it will try to return number of entries to the caller. But
> > > The dispatcher kvm vcpu ioctl dispatcher code in kvm_arch_vcpu_ioctl
> > > ignores any output from this function if it sees the error return code.
> > >
> > > It's very explicit by the code that it was designed to receive some
> > > small number of entries to return E2BIG along with the corrected number.
> > >
> > > This lost logic in the dispatcher code has been restored by removing the
> > > lines that check for function return code and skip if error is found.
> > > Without it, the ioctl caller will see both the number of entries and the
> > > correct error.
> > >
> > > In selftests relevant function vcpu_get_cpuid has also been modified to
> > > utilize the number of cpuid entries returned along with errno E2BIG.
> > >
> > > Signed-off-by: Valeriy Vdovin <valeriy.vdovin@virtuozzo.com>
> > > ---
> > > arch/x86/kvm/x86.c | 10 +++++-----
> > > .../selftests/kvm/lib/x86_64/processor.c | 20 +++++++++++--------
> > > 2 files changed, 17 insertions(+), 13 deletions(-)
> > >
> > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > > index efc7a82ab140..df8a3e44e722 100644
> > > --- a/arch/x86/kvm/x86.c
> > > +++ b/arch/x86/kvm/x86.c
> > > @@ -4773,14 +4773,14 @@ long kvm_arch_vcpu_ioctl(struct file *filp,
> > > r = -EFAULT;
> > > if (copy_from_user(&cpuid, cpuid_arg, sizeof(cpuid)))
> > > goto out;
> > > +
> > > r = kvm_vcpu_ioctl_get_cpuid2(vcpu, &cpuid,
> > > cpuid_arg->entries);
> > > - if (r)
> > > - goto out;
> > > - r = -EFAULT;
> > > - if (copy_to_user(cpuid_arg, &cpuid, sizeof(cpuid)))
> >
> > It may make sense to check that 'r == -E2BIG' before trying to write
> > anything back. I don't think it is correct/expected to modify nent in
> > other cases (e.g. when kvm_vcpu_ioctl_get_cpuid2() returns -EFAULT)
> >
> That's a good point. The caller could expect and rely on the fact that nent
> is unmodified in any error case except E2BIG. I will add this in the next
> version.
> > > +
> > > + if (copy_to_user(cpuid_arg, &cpuid, sizeof(cpuid))) {
> > > + r = -EFAULT;
> > > goto out;
> > > - r = 0;
> > > + }
> > > break;
> >
> > How is KVM userspace supposed to know if it can trust the 'nent' value
> > (KVM is fixed case) or not (KVM is not fixed case)? This can probably be
> > resolved with adding a new capability (but then I'm not sure the change
> > is worth it to be honest).
>
> As I see it KVM userspace should set nent to 0, and then expect any non-zero
> value in return along with E2BIG. This is the same approach I've used in the
> modified test code in the same patch.
IMO, the current code is correct (well, least awful), albeit misleading.
Copying back the number of entries but not the entries themselves would be a bug.
That can obviously be remedied, but it adds even more complexity for no known
benefit, and training userspace to go spelunking on -E2BIG would likely yield
more bugs in the future.
I also think we should keep the -E2BIG behavior of KVM_GET_CPUID2 and
KVM_GET_{SUPPORTED,EMULATED,SUPPORTED_HV}_CPUID consistent. Returning partial
information would make KVM_GET_CPUID2 an anomaly.
diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
index c96f79c9fff2..c4dbc7c47b17 100644
--- a/arch/x86/kvm/cpuid.c
+++ b/arch/x86/kvm/cpuid.c
@@ -348,20 +348,15 @@ int kvm_vcpu_ioctl_get_cpuid2(struct kvm_vcpu *vcpu,
struct kvm_cpuid2 *cpuid,
struct kvm_cpuid_entry2 __user *entries)
{
- int r;
-
- r = -E2BIG;
if (cpuid->nent < vcpu->arch.cpuid_nent)
- goto out;
- r = -EFAULT;
+ return -E2BIG;
+
if (copy_to_user(entries, vcpu->arch.cpuid_entries,
vcpu->arch.cpuid_nent * sizeof(struct kvm_cpuid_entry2)))
- goto out;
- return 0;
+ return -EFAULT;
-out:
cpuid->nent = vcpu->arch.cpuid_nent;
- return r;
+ return 0;
}
/* Mask kvm_cpu_caps for @leaf with the raw CPUID capabilities of this CPU. */
prev parent reply other threads:[~2021-04-28 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 11:36 [PATCH] KVM: x86: Fix KVM_GET_CPUID2 ioctl to return cpuid entries count Valeriy Vdovin
2021-04-28 12:38 ` Vitaly Kuznetsov
2021-04-28 13:46 ` Valeriy Vdovin
2021-04-28 14:58 ` Sean Christopherson [this message]
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=YIl4M/GgaYvwNuXv@google.com \
--to=seanjc@google.com \
--cc=aaronlewis@google.com \
--cc=bp@alien8.de \
--cc=den@openvz.org \
--cc=drjones@redhat.com \
--cc=graf@amazon.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=like.xu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=valeriy.vdovin@virtuozzo.com \
--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