From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757083Ab2GQV7c (ORCPT ); Tue, 17 Jul 2012 17:59:32 -0400 Received: from mail-gg0-f174.google.com ([209.85.161.174]:34219 "EHLO mail-gg0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755382Ab2GQV71 (ORCPT ); Tue, 17 Jul 2012 17:59:27 -0400 Subject: Patch "hrtimers: Move lock held region in hrtimer_interrupt()" has been added to the 3.4-stable tree To: johnstul@us.ibm.com, a.p.zijlstra@chello.nl, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, mingo@kernel.org, prarit@redhat.com, tglx@linutronix.de Cc: , From: Date: Tue, 17 Jul 2012 14:59:19 -0700 In-Reply-To: <1342507196-54327-5-git-send-email-johnstul@us.ibm.com> Message-ID: <13425623591800@kroah.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This is a note to let you know that I've just added the patch titled hrtimers: Move lock held region in hrtimer_interrupt() to the 3.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: hrtimers-move-lock-held-region-in-hrtimer_interrupt.patch and it can be found in the queue-3.4 subdirectory. If you, or anyone else, feels it should not be added to the stable tree, please let know about it. >>From johnstul@us.ibm.com Tue Jul 17 14:27:06 2012 From: John Stultz Date: Tue, 17 Jul 2012 02:39:53 -0400 Subject: hrtimers: Move lock held region in hrtimer_interrupt() To: stable@vger.kernel.org Cc: Thomas Gleixner , John Stultz , Prarit Bhargava , Linux Kernel Message-ID: <1342507196-54327-5-git-send-email-johnstul@us.ibm.com> From: Thomas Gleixner This is a backport of 196951e91262fccda81147d2bcf7fdab08668b40 We need to update the base offsets from this code and we need to do that under base->lock. Move the lock held region around the ktime_get() calls. The ktime_get() calls are going to be replaced with a function which gets the time and the offsets atomically. Signed-off-by: Thomas Gleixner Reviewed-by: Ingo Molnar Acked-by: Peter Zijlstra Acked-by: Prarit Bhargava Signed-off-by: John Stultz Link: http://lkml.kernel.org/r/1341960205-56738-6-git-send-email-johnstul@us.ibm.com Signed-off-by: Thomas Gleixner Cc: Prarit Bhargava Cc: Thomas Gleixner Signed-off-by: John Stultz Signed-off-by: Greg Kroah-Hartman --- kernel/hrtimer.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) --- a/kernel/hrtimer.c +++ b/kernel/hrtimer.c @@ -1263,11 +1263,10 @@ void hrtimer_interrupt(struct clock_even cpu_base->nr_events++; dev->next_event.tv64 = KTIME_MAX; + raw_spin_lock(&cpu_base->lock); entry_time = now = ktime_get(); retry: expires_next.tv64 = KTIME_MAX; - - raw_spin_lock(&cpu_base->lock); /* * We set expires_next to KTIME_MAX here with cpu_base->lock * held to prevent that a timer is enqueued in our queue via @@ -1344,6 +1343,7 @@ retry: * interrupt routine. We give it 3 attempts to avoid * overreacting on some spurious event. */ + raw_spin_lock(&cpu_base->lock); now = ktime_get(); cpu_base->nr_retries++; if (++retries < 3) @@ -1356,6 +1356,7 @@ retry: */ cpu_base->nr_hangs++; cpu_base->hang_detected = 1; + raw_spin_unlock(&cpu_base->lock); delta = ktime_sub(now, entry_time); if (delta.tv64 > cpu_base->max_hang_time.tv64) cpu_base->max_hang_time = delta; Patches currently in stable-queue which might be from johnstul@us.ibm.com are queue-3.4/timekeeping-fix-leapsecond-triggered-load-spike-issue.patch queue-3.4/hrtimer-update-hrtimer-base-offsets-each-hrtimer_interrupt.patch queue-3.4/timekeeping-add-missing-update-call-in-timekeeping_resume.patch queue-3.4/hrtimers-move-lock-held-region-in-hrtimer_interrupt.patch queue-3.4/hrtimer-provide-clock_was_set_delayed.patch queue-3.4/timekeeping-provide-hrtimer-update-function.patch queue-3.4/timekeeping-maintain-ktime_t-based-offsets-for-hrtimers.patch