public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Uli Luckas <u.luckas@road.de>
Cc: Chris Wright <chrisw@sous-sol.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21.5 june 30th to july 1st date hang?
Date: Wed, 4 Jul 2007 09:53:13 -0700	[thread overview]
Message-ID: <20070704165313.GC4306@sequoia.sous-sol.org> (raw)
In-Reply-To: <200707041056.53992.u.luckas@road.de>

* Uli Luckas (u.luckas@road.de) wrote:
> On Tuesday, 3. July 2007, Chuck Ebbert wrote:
> > On 07/03/2007 03:28 PM, Chris Friesen wrote:
> > > Arne Georg Gleditsch wrote:
> > >> An interesting exercise might be to
> > >> code up a small program to call adjtimex with timex.status |= STA_INS,
> > >> to see if this can trigger the problem.
> > >
> > > Setting the date to just before midnight June 30 UTC and then running
> > > the following as root triggered the crash on a modified 2.6.10.  Anyone
> > > see anything wrong with the code below, or is this a valid indication of
> > > a bug in the leap second code?
> >
> > Fixed:
> > http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm
> >itdiff;h=746976a301ac9c9aa10d7d42454f8d6cdad8ff2b
> >
> Hi Chris,
> does that qualify for inclusion into 2.6.21.6?

Yes, it has already been sent to -stable.

thanks,
-chris

  reply	other threads:[~2007-07-04 16:53 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 12:44 2.6.21.5 june 30th to july 1st date hang? Fortier,Vincent [Montreal]
2007-07-03 12:55 ` Fortier,Vincent [Montreal]
2007-07-03 13:05 ` Clemens Koller
2007-07-03 14:51   ` Fortier,Vincent [Montreal]
2007-07-03 13:56 ` Uli Luckas
2007-07-03 13:59 ` Florian Attenberger
2007-07-03 14:20   ` Arne Georg Gleditsch
2007-07-03 15:02     ` Florian Attenberger
2007-07-03 15:26       ` Arne Georg Gleditsch
2007-07-03 15:36         ` Fortier,Vincent [Montreal]
2007-07-03 17:19           ` Dave Jones
2007-07-03 19:28         ` Chris Friesen
2007-07-03 21:02           ` Chris Friesen
2007-07-03 21:02           ` Chuck Ebbert
2007-07-04  1:06             ` Fortier,Vincent [Montreal]
2007-07-04  8:56             ` Uli Luckas
2007-07-04 16:53               ` Chris Wright [this message]
2007-07-05 14:13                 ` Clemens Koller
2007-07-05 17:48                   ` Chris Friesen
2007-07-05 18:34                     ` Clemens Koller
2007-07-05 20:10                     ` Thomas Gleixner
2007-07-05 21:02                       ` Chris Friesen
2007-07-05 21:17                         ` Thomas Gleixner
2007-07-05 22:28                     ` Ernie Petrides
2007-07-05 22:49                       ` Chris Friesen
2007-07-05 23:12                         ` Ernie Petrides
2007-07-05 23:45                           ` Chris Friesen
2007-07-06  5:16                             ` Thomas Gleixner
2007-07-06  5:17                           ` Thomas Gleixner
2007-07-06 15:47                             ` Chris Friesen
2007-07-06 20:03                             ` Ernie Petrides
2007-07-03 15:59 ` Chris Friesen
2007-07-03 16:00   ` Fortier,Vincent [Montreal]
2007-07-03 16:03     ` Chris Friesen
2007-07-03 17:28       ` Chris Friesen

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=20070704165313.GC4306@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=u.luckas@road.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