All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH 0/4] KVM: x86: fix bugs reported by Dan Carpenter
Date: Thu, 18 May 2017 21:25:07 +0200	[thread overview]
Message-ID: <20170518192506.GA1819@potion> (raw)
In-Reply-To: <320c57ae-184d-3123-e77f-63f159e44d49@redhat.com>

2017-05-18 20:52+0200, Paolo Bonzini:
> On 18/05/2017 19:37, Radim Krčmář wrote:
> > It would be possible to make reproducers for the first three patches,
> > but they happen under circumstances too remote from normal use, so I
> > didn't test them like that. :)
> > 
> > 
> > Radim Krčmář (4):
> >   KVM: nVMX: fix nested_vmx_check_vmptr failure paths under debugging
> >   KVM: x86: zero base3 of unusable segments
> >   KVM: x86/vPMU: fix undefined shift in intel_pmu_refresh()
> >   KVM: x86: prevent uninitialized variable warning in check_svme()
> > 
> >  arch/x86/kvm/emulate.c   |  2 +-
> >  arch/x86/kvm/pmu_intel.c |  2 +-
> >  arch/x86/kvm/vmx.c       | 31 ++++++++++++++++++-------------
> >  arch/x86/kvm/x86.c       |  2 ++
> >  4 files changed, 22 insertions(+), 15 deletions(-)
> > 
> 
> Patch 1 is ugly, but I don't have any better idea.

I agree.  Adding another argument was clearly worse, but I almost chose
to keep the skip in nested_vmx_check_vmptr() and return it +1, to signal
an error, and then subtract 1 before returning from the exit handler.

> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

Thanks.

      reply	other threads:[~2017-05-18 19:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 17:37 [PATCH 0/4] KVM: x86: fix bugs reported by Dan Carpenter Radim Krčmář
2017-05-18 17:37 ` [PATCH 1/4] KVM: nVMX: fix nested_vmx_check_vmptr failure paths under debugging Radim Krčmář
2017-05-19 13:48   ` [PATCH v2] " Radim Krčmář
2017-05-30 14:34     ` Paolo Bonzini
2017-05-18 17:37 ` [PATCH 2/4] KVM: x86: zero base3 of unusable segments Radim Krčmář
2017-05-19 13:30   ` David Hildenbrand
2017-05-18 17:37 ` [PATCH 3/4] KVM: x86/vPMU: fix undefined shift in intel_pmu_refresh() Radim Krčmář
2017-05-19 13:31   ` David Hildenbrand
2017-05-18 17:37 ` [PATCH 4/4] KVM: x86: prevent uninitialized variable warning in check_svme() Radim Krčmář
2017-05-19 13:32   ` David Hildenbrand
2017-05-18 18:52 ` [PATCH 0/4] KVM: x86: fix bugs reported by Dan Carpenter Paolo Bonzini
2017-05-18 19:25   ` Radim Krčmář [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=20170518192506.GA1819@potion \
    --to=rkrcmar@redhat.com \
    --cc=dan.carpenter@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.