kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Paolo Bonzini <pbonzini@redhat.com>,
	Christoffer Dall <christoffer.dall@linaro.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	"ego@linux.vnet.ibm.com" <ego@linux.vnet.ibm.com>
Subject: Re: [PATCH] arm, kvm: fix double lock on cpu_add_remove_lock
Date: Mon, 07 Apr 2014 12:14:22 +0530	[thread overview]
Message-ID: <53424946.4000504@linux.vnet.ibm.com> (raw)
In-Reply-To: <1396805768-18669-1-git-send-email-tom.leiming@gmail.com>

On 04/06/2014 11:06 PM, Ming Lei wrote:
> The patch of "arm, kvm: Fix CPU hotplug callback registration"
> in -next tree holds the lock before calling the two functions:
> 
> 	kvm_vgic_hyp_init()
> 	kvm_timer_hyp_init()
> 
> and both the two functions are calling register_cpu_notifier()
> to register cpu notifier, so cause double lock on cpu_add_remove_lock.
> 
> Considered that both two functions are only called inside
> kvm_arch_init() with holding cpu_add_remove_lock, so simply use
> __register_cpu_notifier() to fix the problem.
> 
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Christoffer Dall <christoffer.dall@linaro.org>
> Cc: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
> Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Signed-off-by: Ming Lei <tom.leiming@gmail.com>

Sorry for missing that, and thank you for the fix!

Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>

Regards,
Srivatsa S. Bhat

> ---
>  virt/kvm/arm/arch_timer.c |    2 +-
>  virt/kvm/arm/vgic.c       |    2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
> index 5081e80..22fa819 100644
> --- a/virt/kvm/arm/arch_timer.c
> +++ b/virt/kvm/arm/arch_timer.c
> @@ -277,7 +277,7 @@ int kvm_timer_hyp_init(void)
> 
>  	host_vtimer_irq = ppi;
> 
> -	err = register_cpu_notifier(&kvm_timer_cpu_nb);
> +	err = __register_cpu_notifier(&kvm_timer_cpu_nb);
>  	if (err) {
>  		kvm_err("Cannot register timer CPU notifier\n");
>  		goto out_free;
> diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c
> index 8ca405c..47b2983 100644
> --- a/virt/kvm/arm/vgic.c
> +++ b/virt/kvm/arm/vgic.c
> @@ -1496,7 +1496,7 @@ int kvm_vgic_hyp_init(void)
>  		goto out;
>  	}
> 
> -	ret = register_cpu_notifier(&vgic_cpu_nb);
> +	ret = __register_cpu_notifier(&vgic_cpu_nb);
>  	if (ret) {
>  		kvm_err("Cannot register vgic CPU notifier\n");
>  		goto out_free_irq;
> 

  reply	other threads:[~2014-04-07  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-06 17:36 [PATCH] arm, kvm: fix double lock on cpu_add_remove_lock Ming Lei
2014-04-07  6:44 ` Srivatsa S. Bhat [this message]
2014-04-08 11:33   ` Rafael J. Wysocki

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=53424946.4000504@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=ego@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tom.leiming@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).