From: Ben Hutchings <ben@decadent.org.uk>
To: John Stultz <johnstul@us.ibm.com>
Cc: stable@vger.kernel.org,
Richard Cochran <richardcochran@gmail.com>,
Dave Jones <davej@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -stable] ntp: Correct TAI offset during leap second
Date: Sun, 17 Jun 2012 15:43:43 +0100 [thread overview]
Message-ID: <1339944223.4942.240.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <4FDB8563.3030805@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Fri, 2012-06-15 at 11:56 -0700, John Stultz wrote:
> Hey Greg,
> Forgot to cc stable on this one. Thanks to Dave Jones for noticing!
> -john
>
> ------------------
>
> From: Richard Cochran<richardcochran@gmail.com>
>
> commit dd48d708ff3e917f6d6b6c2b696c3f18c019feed upstream.
>
> When repeating a UTC time value during a leap second (when the UTC
>
> time should be 23:59:60), the TAI timescale should not stop. The kernel
>
> NTP code increments the TAI offset one second too late. This patch fixes
>
> the issue by incrementing the offset during the leap second itself.
[...]
This doesn't apply to 3.2.y, unsurprisingly. Let me know if there are
any urgent leap second fixes that will be needed there.
Ben.
--
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at once.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-06-17 14:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 18:56 John Stultz
2012-06-15 19:01 ` John Stultz
2012-06-17 14:43 ` Ben Hutchings [this message]
2012-06-17 16:47 ` Jonathan Nieder
2012-06-17 17:34 ` Richard Cochran
2012-06-18 13:55 ` Ben Hutchings
2012-06-18 16:28 ` Richard Cochran
2012-06-19 11:54 ` Ben Hutchings
2012-06-19 17:26 ` John Stultz
2012-06-20 16:25 ` Richard Cochran
2012-06-20 16:42 ` John Stultz
2012-06-18 18:20 ` John Stultz
2012-06-19 11:57 ` Ben Hutchings
2012-07-01 1:28 ` Ben Hutchings
2012-07-01 5:27 ` 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=1339944223.4942.240.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=davej@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®