nohz: Make tick_nohz_irq_exit() irq safe
Frederic Weisbecker [Wed, 20 Feb 2013 15:15:36 +0000 (16:15 +0100)]
commit e5ab012c3271990e8457055c25cafddc1ae8aa6b upstream.

As it stands, irq_exit() may or may not be called with
irqs disabled, depending on __ARCH_IRQ_EXIT_IRQS_DISABLED
that the arch can define.

It makes tick_nohz_irq_exit() unsafe. For example two
interrupts can race in tick_nohz_stop_sched_tick(): the inner
most one computes the expiring time on top of the timer list,
then it's interrupted right before reprogramming the
clock. The new interrupt enqueues a new timer list timer,
it reprogram the clock to take it into account and it exits.
The CPUs resumes the inner most interrupt and performs the clock
reprogramming without considering the new timer list timer.

This regression has been introduced by:
     ("nohz: Separate out irq exit and idle loop dyntick logic")

Let's fix it right now with the appropriate protections.

A saner long term solution will be to remove
__ARCH_IRQ_EXIT_IRQS_DISABLED and mandate that irq_exit() is called
with interrupts disabled.

Signed-off-by: Frederic Weisbecker <>
Cc: Peter Zijlstra <>
Cc: Ingo Molnar <>
Cc: Linus Torvalds <>
Signed-off-by: Thomas Gleixner <>
Signed-off-by: Greg Kroah-Hartman <>
Signed-off-by: Thomas Gleixner <>
Signed-off-by: Lingzhu Xiang <>
Reviewed-by: CAI Qian <>
Signed-off-by: Greg Kroah-Hartman <>


index e603477..01d8e62 100644 (file)
@@ -496,12 +496,17 @@ void tick_nohz_idle_enter(void)
 void tick_nohz_irq_exit(void)
+       unsigned long flags;
        struct tick_sched *ts = &__get_cpu_var(tick_cpu_sched);
        if (!ts->inidle)
+       local_irq_save(flags);
+       local_irq_restore(flags);