[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200707052228.l65MSdvA025440@pasta.boston.redhat.com>
Date: Thu, 05 Jul 2007 18:28:39 -0400
From: Ernie Petrides <petrides@...hat.com>
To: "Chris Friesen" <cfriesen@...tel.com>
cc: Clemens Koller <clemens.koller@...gramm.de>,
Chris Wright <chrisw@...s-sol.org>,
Uli Luckas <u.luckas@...d.de>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.21.5 june 30th to july 1st date hang?
On Thursday, 5-Jul-2007 at 11:48 MDT, "Chris Friesen" wrote:
> Clemens Koller wrote:
>
> > Okay, we all survived Y2K and this little glitch. Puh! ;-)
> > Can you please explain in which configuration this problem got triggered.
>
> As far as I can tell many kernel versions contained the source code bug.
> (I'd like some more information on exactly what the problem was if
> anyone cares to share..the proposed patch didn't give much in the way of
> specifics.)
>
> However, in order to trigger the problem you also need to have NTP
> servers that were erroneously broadcasting the addition of a leap second.
>
> So most people didn't see the issue because there wasn't supposed to be
> a leap second added this year...but they would have seen it the next
> time a leap second was added.
Only kernels built with the CONFIG_HIGH_RES_TIMERS option enabled were
vulnerable.
Cheers. -ernie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists