public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yu Zhang <yu.c.zhang@linux.intel.com>
To: Jim Mattson <jmattson@google.com>,
	David Hildenbrand <david@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: "kvm list" <kvm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"H . Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] KVM: x86: Fix the NULL pointer parameter in check_cr_write()
Date: Wed, 20 Sep 2017 14:35:30 +0800	[thread overview]
Message-ID: <0a2a586b-5dd6-88cb-bd22-f0676b1c8fbe@linux.intel.com> (raw)
In-Reply-To: <CALMp9eS3X3owa7ue5+jpz8bi-Sgp5MWGTj7DvFMLWBqErgDNOg@mail.gmail.com>



On 9/18/2017 11:56 PM, Jim Mattson wrote:
> kvm_cpuid ultimately wants to write all four of the GPRs passed in by
> reference. I don't see any advantage to allowing some of these
> pointers to be NULL.

Thanks for your comments, Jim & David.

2 reasons I did not choose to change kvm_cpuid():
1> like Jim's comments, kvm_cpuid() will eventually write the *eax - 
*edx no matter
a cpuid entry is found or not;
2> currently, return value of kvm_cpuid() is either true when an entry 
is found or false
otherwise. We can change kvm_cpuid() to check the pointers of GPRs 
against NULL and
return false immediately. Then the false value would have 2 different 
meanings - entry
not found, or invalid params.

Paolo, any suggestion? :-)

Thanks
Yu

> Reviewed-by: Jim Mattson <jmattson@google.com>
>
> On Mon, Sep 18, 2017 at 5:19 AM, David Hildenbrand <david@redhat.com> wrote:
>> On 18.09.2017 12:45, Yu Zhang wrote:
>>> Routine check_cr_write() will trigger emulator_get_cpuid()->
>>> kvm_cpuid() to get maxphyaddr, and NULL is passed as values
>>> for ebx/ecx/edx. This is problematic because kvm_cpuid() will
>>> dereference these pointers.
>>>
>>> Fixes: d1cd3ce90044 ("KVM: MMU: check guest CR3 reserved bits based on its physical address width.")
>>> Reported-by: Jim Mattson <jmattson@google.com>
>>> Signed-off-by: Yu Zhang <yu.c.zhang@linux.intel.com>
>>> ---
>>>   arch/x86/kvm/emulate.c | 8 +++++---
>>>   1 file changed, 5 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
>>> index 16bf665..15f527b 100644
>>> --- a/arch/x86/kvm/emulate.c
>>> +++ b/arch/x86/kvm/emulate.c
>>> @@ -4102,10 +4102,12 @@ static int check_cr_write(struct x86_emulate_ctxt *ctxt)
>>>                ctxt->ops->get_msr(ctxt, MSR_EFER, &efer);
>>>                if (efer & EFER_LMA) {
>>>                        u64 maxphyaddr;
>>> -                     u32 eax = 0x80000008;
>>> +                     u32 eax, ebx, ecx, edx;
>>>
>>> -                     if (ctxt->ops->get_cpuid(ctxt, &eax, NULL, NULL,
>>> -                                              NULL, false))
>>> +                     eax = 0x80000008;
>>> +                     ecx = 0;
>>> +                     if (ctxt->ops->get_cpuid(ctxt, &eax, &ebx, &ecx,
>>> +                                              &edx, false))
>>>                                maxphyaddr = eax & 0xff;
>>>                        else
>>>                                maxphyaddr = 36;
>>>
>> Not sure if fixing kvm_cpuid() would be better.
>>
>> Reviewed-by: David Hildenbrand <david@redhat.com>
>>
>> --
>>
>> Thanks,
>>
>> David

  reply	other threads:[~2017-09-20  6:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 10:45 [PATCH] KVM: x86: Fix the NULL pointer parameter in check_cr_write() Yu Zhang
2017-09-18 12:19 ` David Hildenbrand
2017-09-18 15:56   ` Jim Mattson
2017-09-20  6:35     ` Yu Zhang [this message]
2017-09-20  8:13       ` Paolo Bonzini
2017-09-20  8:27         ` Yu Zhang

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=0a2a586b-5dd6-88cb-bd22-f0676b1c8fbe@linux.intel.com \
    --to=yu.c.zhang@linux.intel.com \
    --cc=david@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    /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