From: John Stultz <johnstul@us.ibm.com>
To: stable@vger.kernel.org
Cc: John Stultz <johnstul@us.ibm.com>,
Prarit Bhargava <prarit@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/7] 3.4-stable: Fix for leapsecond caused hrtimer/futex issue
Date: Tue, 17 Jul 2012 02:39:49 -0400 [thread overview]
Message-ID: <1342507196-54327-1-git-send-email-johnstul@us.ibm.com> (raw)
Here is backport of the leapsecond fixes to 3.4-stable. These are very
straight forward, and backported to 3.4.x with no collisions or changes.
This patchset resolve the early hrtimer/futex expiration issue
widely seen after the June 30th leapsecond.
I've booted and tested this patchset on two boxes and run through a number
of leapsecond related stress tests. However, additional testing and review
would be appreciated.
The original commits backported in this set are:
f55a6faa384304c89cfef162768e88374d3312cb hrtimer: Provide clock_was_set_delayed()
4873fa070ae84a4115f0b3c9dfabc224f1bc7c51 timekeeping: Fix leapsecond triggered load spike issue
5b9fe759a678e05be4937ddf03d50e950207c1c0 timekeeping: Maintain ktime_t based offsets for hrtimers
196951e91262fccda81147d2bcf7fdab08668b40 hrtimers: Move lock held region in hrtimer_interrupt()
f6c06abfb3972ad4914cef57d8348fcb2932bc3b timekeeping: Provide hrtimer update function
5baefd6d84163443215f4a99f6a20f054ef11236 hrtimer: Update hrtimer base offsets each hrtimer_interrupt
3e997130bd2e8c6f5aaa49d6e3161d4d29b43ab0 timekeeping: Add missing update call in timekeeping_resume()
I've already done backports to all the stable kernels to 2.6.32,
and will be sending them out shortly.
Please let me know if you have any comments or feedback.
thanks
-john
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
John Stultz (3):
3.4.x: hrtimer: Provide clock_was_set_delayed()
3.4.x: timekeeping: Fix leapsecond triggered load spike issue
3.4.x: hrtimer: Update hrtimer base offsets each hrtimer_interrupt
Thomas Gleixner (4):
3.4.x: timekeeping: Maintain ktime_t based offsets for hrtimers
3.4.x: hrtimers: Move lock held region in hrtimer_interrupt()
3.4.x: timekeeping: Provide hrtimer update function
3.4.x: timekeeping: Add missing update call in timekeeping_resume()
include/linux/hrtimer.h | 10 ++++++-
kernel/hrtimer.c | 53 +++++++++++++++++++++++++------------
kernel/time/timekeeping.c | 64 +++++++++++++++++++++++++++++++++++++++++++--
3 files changed, 108 insertions(+), 19 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-07-17 6:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 6:39 John Stultz [this message]
2012-07-17 6:39 ` [PATCH 1/7] 3.4.x: hrtimer: Provide clock_was_set_delayed() John Stultz
2012-07-17 21:59 ` Patch "hrtimer: Provide clock_was_set_delayed()" has been added to the 3.4-stable tree gregkh
2012-07-17 6:39 ` [PATCH 2/7] 3.4.x: timekeeping: Fix leapsecond triggered load spike issue John Stultz
2012-07-17 21:59 ` Patch "timekeeping: Fix leapsecond triggered load spike issue" has been added to the 3.4-stable tree gregkh
2012-07-17 6:39 ` [PATCH 3/7] 3.4.x: timekeeping: Maintain ktime_t based offsets for hrtimers John Stultz
2012-07-17 21:59 ` Patch "timekeeping: Maintain ktime_t based offsets for hrtimers" has been added to the 3.4-stable tree gregkh
2012-07-17 6:39 ` [PATCH 4/7] 3.4.x: hrtimers: Move lock held region in hrtimer_interrupt() John Stultz
2012-07-17 21:59 ` Patch "hrtimers: Move lock held region in hrtimer_interrupt()" has been added to the 3.4-stable tree gregkh
2012-07-17 6:39 ` [PATCH 5/7] 3.4.x: timekeeping: Provide hrtimer update function John Stultz
2012-07-17 21:59 ` Patch "timekeeping: Provide hrtimer update function" has been added to the 3.4-stable tree gregkh
2012-07-17 6:39 ` [PATCH 6/7] 3.4.x: hrtimer: Update hrtimer base offsets each hrtimer_interrupt John Stultz
2012-07-17 21:59 ` Patch "hrtimer: Update hrtimer base offsets each hrtimer_interrupt" has been added to the 3.4-stable tree gregkh
2012-07-17 6:39 ` [PATCH 7/7] 3.4.x: timekeeping: Add missing update call in timekeeping_resume() John Stultz
2012-07-17 21:59 ` Patch "timekeeping: Add missing update call in timekeeping_resume()" has been added to the 3.4-stable tree gregkh
2012-07-17 21:29 ` [PATCH 0/7] 3.4-stable: Fix for leapsecond caused hrtimer/futex issue Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1342507196-54327-1-git-send-email-johnstul@us.ibm.com \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).