From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
stable@vger.kernel.org, Yang Zhang <yang.z.zhang@intel.com>,
Liang Li <liang.z.li@intel.com>
Subject: Re: [PATCH] KVM: VMX: fix vmwrite to invalid VMCS
Date: Tue, 7 Jul 2015 15:55:36 +0200 [thread overview]
Message-ID: <559BDA58.203@redhat.com> (raw)
In-Reply-To: <20150707135012.GA26862@potion.brq.redhat.com>
On 07/07/2015 15:50, Radim Krčmář wrote:
>> Andrey reported offlist that the bug went away by reverting 1cde293. So
>> the patch would at least need a new commit message. :)
>
> I think it's a different bug than the one Andrey reproduced
> (https://bugzilla.kernel.org/show_bug.cgi?id=100671).
> I'll send a v2 that cleans up the code and makes the commit message
> clearer, unless you find the reasoning below unsound.
Yes, the patch is okay. The problem is that kvm-arch_vcpu_create is
called from a VM ioctl and thus is not between vcpu_load and vcpu_put.
Thanks, I applied it.
Paolo
> This bug is specific to 'kvm_arch_vcpu_create()' and Vlastimil Holer hit
> it on RHEL 7.2 (278.el7) kernel that didn't have 1cde2930e154
> ("sched/preempt: Add static_key() to preempt_notifiers").
>
> The commit message does not base on tracing (I haven't reproduced it),
> but I couldn't make sense out of this bug otherwise.
> I think it happens just because other VCPU preempted the new one between
> vmx_vcpu_put()+put_cpu() and the end of kvm_x86_ops->fpu_activate(), so
> vmwrite accessed different VMCS. The code in kvm_vm_ioctl_create_vcpu()
> that made me think so:
>
> vcpu = kvm_arch_vcpu_create(id) {
> vcpu = kvm_x86_ops->vcpu_create(kvm, id) {
> vmx = kmem_cache_zalloc(kvm_vcpu_cache, GFP_KERNEL);
> kvm_vcpu_init(&vmx->vcpu, kvm, id);
> vmx->loaded_vmcs = &vmx->vmcs01;
> vmx->loaded_vmcs->vmcs = alloc_vmcs();
> loaded_vmcs_init(vmx->loaded_vmcs);
>
> // disabling preemption and activating VMCS
> cpu = get_cpu();
> vmx_vcpu_load(&vmx->vcpu, cpu);
>
> vmx_vcpu_setup(vmx);
>
> // abandoning VMCS and enabling preemption
> vmx_vcpu_put(&vmx->vcpu);
> put_cpu();
>
> return &vmx->vcpu;
> }
>
> // enabled preemption and undefined current VMCS
> kvm_x86_ops->fpu_activate(vcpu);
> return vcpu;
> }
>
> preempt_notifier_init(&vcpu->preempt_notifier, &kvm_preempt_ops);
> kvm_arch_vcpu_setup(vcpu) {
> vcpu_load(vcpu);
> ...
> }
>
prev parent reply other threads:[~2015-07-07 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 13:49 [PATCH] KVM: VMX: fix vmwrite to invalid VMCS Radim Krčmář
2015-07-03 15:12 ` Paolo Bonzini
2015-07-07 13:50 ` Radim Krčmář
2015-07-07 13:55 ` Paolo Bonzini [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=559BDA58.203@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=liang.z.li@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.org \
--cc=yang.z.zhang@intel.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.