This issue stemmed from the timekeeping subsystem not notifying
the hrtimer subsystem that the leapsecond occurred, causing
CLOCK_REALTIME hritmers to be fired one second early, and
sub-second CLOCK_REALTIME hrtimer timeouts to fire immediately
(causing the load spikes).
To address this issue I'm proposing we do three things:
1) Fix the clock_was_set() call to remove the limitation that kept
us from calling it from update_wall_time().
2) Call clock_was_set() when we add/remove a leapsecond.
3) Change hrtimer_interrupt to update the hrtimer base offset values.
This third item provides additional robustness should the
clock_was_set() notification (done via a timer if we're in_atomic)
be delayed significantly.
NOTE: Some reports have been of a hard hang right at or before
the leapsecond. I've not been able to reproduce or diagnose
this, so this fix does not likely address the reported hard
hangs (unless they end up being connected to the futex/hrtimer
issue). Please email lkml and me if you experienced this.
Big thanks to Prarit for shaking out a few issues in the earlier
version of this patch set, as well as the extra effort testing over
Also, I've already got backports generated for -stable, that I'm
testing and I'll submitting them once I have upstream commit ids for
CC: Prarit Bhargava <firstname.lastname@example.org>
CC: Thomas Gleixner <email@example.com>
John Stultz (3):
hrtimer: Fix clock_was_set so it is safe to call from irq context
time: Fix leapsecond triggered hrtimer/futex load spike issue
hrtimer: Update hrtimer base offsets each hrtimer_interrupt
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/