On 07/04/2012 02:21 AM, John Stultz wrote: > As widely reported on the internet, some Linux systems after > the leapsecond was inserted are experiencing futex related load > spikes (usually connected to MySQL, Firefox, Thunderbird, Java, etc). > > An apparent for this issue workaround is running: > $ date -s "`date`" > > Credit: http://www.sheeri.com/content/mysql-and-leap-second-high-cpu-and-fix > > I this issue is due to the leapsecond being added without > calling clock_was_set() to notify the hrtimer subsystem of the > change. > > The workaround functions as it forces a clock_was_set() > call from settimeofday(). > > This fix adds the required clock_was_set() calls to where > we adjust for leapseconds. > > NOTE: This fix *depends* on the previous fix, which allows > clock_was_set to be called from atomic context. Do not try > to apply just this patch. > > CC: Prarit Bhargava <[email protected]> > CC: [email protected] > CC: Thomas Gleixner <[email protected]> > CC: [email protected] > Reported-by: Jan Engelhardt <[email protected]> > Signed-off-by: John Stultz <[email protected]>
Acked-by: Prarit Bhargava <[email protected]> P. -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
