All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: John Stultz <johnstul@us.ibm.com>,
	stable@vger.kernel.org, Sasha Levin <levinsasha928@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	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 11:47:51 -0500	[thread overview]
Message-ID: <20120617164751.GJ12429@burratino> (raw)
In-Reply-To: <1339944223.4942.240.camel@deadeye.wl.decadent.org.uk>

Ben Hutchings wrote:
> On Fri, 2012-06-15 at 11:56 -0700, John Stultz wrote:

>> commit dd48d708ff3e917f6d6b6c2b696c3f18c019feed upstream.
[...]
> 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.

6b43ae8a619d (ntp: Fix leap-second hrtimer livelock) sounds important,
but the patch depends on bd3312681f69 (ntp: Add ntp_lock to replace
xtime_locking) which does not have a commit message explaining its
purpose (and that patch in turn depends on ea7cf49a7633).

John, is that bug present in 3.2.y and 3.0.y, too?  Any hints for
fixing it?

Thanks,
Jonathan

  reply	other threads:[~2012-06-17 16:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 18:56 [PATCH -stable] ntp: Correct TAI offset during leap second John Stultz
2012-06-15 19:01 ` John Stultz
2012-06-17 14:43 ` Ben Hutchings
2012-06-17 16:47   ` Jonathan Nieder [this message]
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=20120617164751.GJ12429@burratino \
    --to=jrnieder@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=davej@redhat.com \
    --cc=johnstul@us.ibm.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardcochran@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.