From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <4FF5A4CC.3050302@redhat.com> Date: Thu, 05 Jul 2012 10:29:32 -0400 From: Prarit Bhargava MIME-Version: 1.0 To: John Stultz CC: Linux Kernel , stable@vger.kernel.org, Thomas Gleixner , linux@openhuawei.org Subject: Re: [PATCH 2/3] [RFC] time: Fix leapsecond triggered hrtimer/futex load spike issue References: <1341382890-42324-1-git-send-email-johnstul@us.ibm.com> <1341382890-42324-3-git-send-email-johnstul@us.ibm.com> In-Reply-To: <1341382890-42324-3-git-send-email-johnstul@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: 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 > CC: stable@vger.kernel.org > CC: Thomas Gleixner > CC: linux@openhuawei.org > Reported-by: Jan Engelhardt > Signed-off-by: John Stultz Acked-by: Prarit Bhargava P.