Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756885AbZAGNqS (ORCPT ); Wed, 7 Jan 2009 08:46:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752025AbZAGNqE (ORCPT ); Wed, 7 Jan 2009 08:46:04 -0500 Received: from hawking.rebel.net.au ([203.20.69.83]:43397 "EHLO hawking.rebel.net.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751826AbZAGNqD (ORCPT ); Wed, 7 Jan 2009 08:46:03 -0500 Message-ID: <4964B20B.4030406@davidnewall.com> Date: Thu, 08 Jan 2009 00:15:47 +1030 From: David Newall User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 To: Alan Cox CC: Nick Andrew , Linas Vepstas , david@lang.hm, Kyle Moffett , Ben Goodger , Robert Hancock , linux-kernel@vger.kernel.org, "Jeffrey J. Kosowsky" , MentalMooMan , Travis Crump , burdell@iruntheinter.net Subject: Re: Bug: Status/Summary of slashdot leap-second crash on new years 2008-2009 References: <496076A9.7030907@davidnewall.com> <4960897D.5030603@davidnewall.com> <4961432A.80509@davidnewall.com> <49614835.7000505@davidnewall.com> <3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com> <20090105143335.GC18055@mail.local.tull.net> <4962BB13.7060304@davidnewall.com> <20090106025125.GB28431@mail.local.tull.net> <20090106094058.64c89586@lxorguk.ukuu.org.uk> <496479EA.1020207@davidnewall.com> <20090107095419.70b78dc7@lxorguk.ukuu.org.uk> <49648163.9060007@davidnewall.com> <20090107105201.054c011f@lxorguk.ukuu.org.uk> In-Reply-To: <20090107105201.054c011f@lxorguk.ukuu.org.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1237 Lines: 35 Alan Cox wrote: >> True but irrelevant because the RTC returns a timestamp. And it's >> quietly understood that the RTC is only an approximation. >> > > You miss the point. > No, I got the point. I see no problem. > The RTC stores the CMOS time in MM DD YY HH:MM:SS format. Yes, which is perfect for mktime(), which knows about leap seconds and so produces the correct time_t. >> However it is now clear that no special kernel support is required for >> leap-seconds, and any such code that's been incorporated needs to be >> removed. Removed I say! >> > > There never has been any. Its all handled (both posix and sane) by glibc. Which is what one would expect. It's reports of crashes and kernel bugs being found and fixed in code to handle leap seconds which lead me to a different understanding. I thought it was said that there's kernel support to handle the leap second flag in NTP's broadcasts, and that that was where the bug was. So. What is the situation? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/