From: Paolo Bonzini <pbonzini@redhat.com>
To: Ignacio Alvarado <ikalvarado@google.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"David Matlack" <dmatlack@google.com>
Subject: Re: [PATCH] KVM: Disable irq while unregistering user notifier
Date: Fri, 4 Nov 2016 10:48:03 +0100 [thread overview]
Message-ID: <91cb7682-cf2a-b90c-b4c6-ea50f58acdc4@redhat.com> (raw)
In-Reply-To: <CACXrx52gER4YOzH8PBV+RxeTuT-Vaeg12AByA96WLG1ZgML_8Q@mail.gmail.com>
On 03/11/2016 23:26, Ignacio Alvarado wrote:
> The risk would still be present since fire_user_return_notifiers could
> potentially run at any time and kvm_on_user return could be called
> from drop_user_return_notifiers either from the kvm_put_kvm path or
> the kvm_arch_exit path.
So, do the unregistration
locals->registered = false;
user_return_notifier_unregister(urn);
first in kvm_on_user_return? Nothing else needs to run with IRQs
disabled, and doing it first prevents reentering the code from
kvm_arch_hardware_disable.
Paolo
> Regards
>
> On Wed, Nov 2, 2016 at 10:25 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>>
>> On 22/10/2016 00:08, Ignacio Alvarado wrote:
>>> Function user_notifier_unregister should be called only once for each
>>> registered user notifier.
>>>
>>> Function kvm_arch_hardware_disable can be executed from an IPI context
>>> which could cause a race condition with a VCPU returning to user mode
>>> and attempting to unregister the notifier.
>>>
>>> Signed-off-by: Ignacio Alvarado <ikalvarado@google.com>
>>
>> Should drop_user_return_notifiers instead be moved to kvm_arch_exit?
>>
>> Thanks,
>>
>> Paolo
>>
>>> ---
>>> arch/x86/kvm/x86.c | 10 ++++++++++
>>> 1 file changed, 10 insertions(+)
>>>
>>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>>> index e375235..51f87f0 100644
>>> --- a/arch/x86/kvm/x86.c
>>> +++ b/arch/x86/kvm/x86.c
>>> @@ -210,7 +210,15 @@ static void kvm_on_user_return(struct user_return_notifier *urn)
>>> struct kvm_shared_msrs *locals
>>> = container_of(urn, struct kvm_shared_msrs, urn);
>>> struct kvm_shared_msr_values *values;
>>> + unsigned long flags;
>>>
>>> + /*
>>> + * Disabling irqs at this point since the following code could be
>>> + * interrupted and executed through kvm_arch_hardware_disable()
>>> + */
>>> + local_irq_save(flags);
>>> + if (!locals->registered)
>>> + goto out;
>>> for (slot = 0; slot < shared_msrs_global.nr; ++slot) {
>>> values = &locals->values[slot];
>>> if (values->host != values->curr) {
>>> @@ -220,6 +228,8 @@ static void kvm_on_user_return(struct user_return_notifier *urn)
>>> }
>>> locals->registered = false;
>>> user_return_notifier_unregister(urn);
>>> +out:
>>> + local_irq_restore(flags);
>>> }
>>>
>>> static void shared_msr_update(unsigned slot, u32 msr)
>>>
>
>
>
next prev parent reply other threads:[~2016-11-04 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 22:08 [PATCH] KVM: Disable irq while unregistering user notifier Ignacio Alvarado
2016-11-02 17:25 ` Paolo Bonzini
2016-11-03 22:26 ` Ignacio Alvarado
2016-11-04 9:48 ` Paolo Bonzini [this message]
2016-11-04 18:56 ` Ignacio Alvarado
2016-11-04 19:15 ` [PATCH v2] " Ignacio Alvarado
2016-11-17 12:42 ` Paolo Bonzini
2016-11-19 19:35 ` Radim Krčmář
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=91cb7682-cf2a-b90c-b4c6-ea50f58acdc4@redhat.com \
--to=pbonzini@redhat.com \
--cc=dmatlack@google.com \
--cc=hpa@zytor.com \
--cc=ikalvarado@google.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@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