public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: nico@linaro.org, tglx@linutronix.de, hpa@zytor.com,
	linux-kernel@vger.kernel.org, mingo@kernel.org,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/core] clockevents: Fix cpu_down()  race for hrtimer based broadcasting
Date: Fri, 03 Apr 2015 16:08:53 +0530	[thread overview]
Message-ID: <551E6DBD.6070401@linux.vnet.ibm.com> (raw)
In-Reply-To: <tip-345527b1edce8df719e0884500c76832a18211c3@git.kernel.org>

On 04/02/2015 08:00 PM, tip-bot for Preeti U Murthy wrote:
> Commit-ID:  345527b1edce8df719e0884500c76832a18211c3
> Gitweb:     http://git.kernel.org/tip/345527b1edce8df719e0884500c76832a18211c3
> Author:     Preeti U Murthy <preeti@linux.vnet.ibm.com>
> AuthorDate: Mon, 30 Mar 2015 14:59:19 +0530
> Committer:  Ingo Molnar <mingo@kernel.org>
> CommitDate: Thu, 2 Apr 2015 14:25:39 +0200
> 
> clockevents: Fix cpu_down() race for hrtimer based broadcasting
> 
> It was found when doing a hotplug stress test on POWER, that the
> machine either hit softlockups or rcu_sched stall warnings.  The
> issue was traced to commit:
> 
>   7cba160ad789 ("powernv/cpuidle: Redesign idle states management")
> 
> which exposed the cpu_down() race with hrtimer based broadcast mode:
> 
>   5d1638acb9f6 ("tick: Introduce hrtimer based broadcast")
> 
> The race is the following:
> 
> Assume CPU1 is the CPU which holds the hrtimer broadcasting duty
> before it is taken down.
> 
> 	CPU0					CPU1
> 
> 	cpu_down()				take_cpu_down()
> 						disable_interrupts()
> 
> 	cpu_die()
> 
> 	while (CPU1 != CPU_DEAD) {
> 		msleep(100);
> 		switch_to_idle();
> 		stop_cpu_timer();
> 		schedule_broadcast();
> 	}
> 
> 	tick_cleanup_cpu_dead()
> 		take_over_broadcast()
> 
> So after CPU1 disabled interrupts it cannot handle the broadcast
> hrtimer anymore, so CPU0 will be stuck forever.
> 
> Fix this by explicitly taking over broadcast duty before cpu_die().
> 
> This is a temporary workaround. What we really want is a callback
> in the clockevent device which allows us to do that from the dying
> CPU by pushing the hrtimer onto a different cpu. That might involve
> an IPI and is definitely more complex than this immediate fix.
> 
> Changelog was picked up from:
> 
>     https://lkml.org/lkml/2015/2/16/213
> 
> Suggested-by: Thomas Gleixner <tglx@linutronix.de>
> Tested-by: Nicolas Pitre <nico@linaro.org>
> Signed-off-by: Preeti U. Murthy <preeti@linux.vnet.ibm.com>
> Cc: linuxppc-dev@lists.ozlabs.org
> Cc: mpe@ellerman.id.au
> Cc: nicolas.pitre@linaro.org
> Cc: peterz@infradead.org
> Cc: rjw@rjwysocki.net
> Fixes: http://linuxppc.10917.n7.nabble.com/offlining-cpus-breakage-td88619.html
> Link: http://lkml.kernel.org/r/20150330092410.24979.59887.stgit@preeti.in.ibm.com
> [ Merged it to the latest timer tree, renamed the callback, tidied up the changelog. ]
> Signed-off-by: Ingo Molnar <mingo@kernel.org>

Can this be marked for stable too please?

Regards
Preeti U Murthy


  reply	other threads:[~2015-04-03 10:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30  9:29 [PATCH V2] clockevents: Fix cpu down race for hrtimer based broadcasting Preeti U Murthy
2015-03-31  3:11 ` Nicolas Pitre
2015-04-02 10:42 ` Ingo Molnar
2015-04-02 11:25   ` Preeti U Murthy
2015-04-02 11:31     ` Ingo Molnar
2015-04-02 11:44       ` Preeti U Murthy
2015-04-02 12:02   ` Peter Zijlstra
2015-04-02 12:12     ` Ingo Molnar
2015-04-02 12:44       ` Preeti U Murthy
2015-04-02 12:58       ` Peter Zijlstra
2015-04-02 14:30 ` [tip:timers/core] clockevents: Fix cpu_down() " tip-bot for Preeti U Murthy
2015-04-03 10:38   ` Preeti U Murthy [this message]
2015-04-03 10:50     ` Ingo Molnar
2015-04-06  4:28       ` Preeti U Murthy

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=551E6DBD.6070401@linux.vnet.ibm.com \
    --to=preeti@linux.vnet.ibm.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=nico@linaro.org \
    --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