From: John Stultz <john.stultz@linaro.org>
To: stable@vger.kernel.org
Cc: John Stultz <john.stultz@linaro.org>,
Prarit Bhargava <prarit@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] 3.4-stable timekeeping fixes merged in 3.6
Date: Tue, 11 Sep 2012 15:04:16 -0400 [thread overview]
Message-ID: <1347390259-54838-1-git-send-email-john.stultz@linaro.org> (raw)
Just wanted to send out a few timekeeping fixes that were merged
in 3.6 which are appropriate for -stable.
This queue backports the following fixes:
-----------------------------------------
cee58483cf56e0ba355fdd97ff5e8925329aa936 time: Move ktime_t overflow checking into timespec_valid_strict
bf2ac312195155511a0f79325515cbb61929898a time: Avoid making adjustments if we haven't accumulated anything
4e8b14526ca7fb046a81c94002c1c43b6fdf0e9b time: Improve sanity checking of timekeeping inputs
I've run these through my timetest suite w/ kvm on both i386
& x86_64. But more testing would be of course appreciated.
https://github.com/johnstultz-work/timetests
I also have patch queues for all the -stable trees that I'll be
sending out as my testing completes for those trees.
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.y: time: Improve sanity checking of timekeeping inputs
3.4.y: time: Avoid making adjustments if we haven't accumulated
anything
3.4.y: time: Move ktime_t overflow checking into
timespec_valid_strict
include/linux/ktime.h | 7 -------
include/linux/time.h | 29 +++++++++++++++++++++++++++--
kernel/time/timekeeping.c | 33 +++++++++++++++++++++++++++++----
3 files changed, 56 insertions(+), 13 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-09-11 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 19:04 John Stultz [this message]
2012-09-11 19:04 ` [PATCH 1/3] 3.4.y: time: Improve sanity checking of timekeeping inputs John Stultz
2012-09-11 19:04 ` [PATCH 2/3] 3.4.y: time: Avoid making adjustments if we haven't accumulated anything John Stultz
2012-09-11 19:04 ` [PATCH 3/3] 3.4.y: time: Move ktime_t overflow checking into timespec_valid_strict John Stultz
2012-09-27 20:33 ` [PATCH 0/3] 3.4-stable timekeeping fixes merged in 3.6 Greg KH
-- strict thread matches above, loose matches on Subject: below --
2012-09-18 1:38 John Stultz
2012-09-18 2:49 ` John Stultz
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=1347390259-54838-1-git-send-email-john.stultz@linaro.org \
--to=john.stultz@linaro.org \
--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