| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 7 Jan 2009 14:10:25 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: David Newall <davidn@...idnewall.com> Cc: Nick Andrew <nick@...k-andrew.net>, Linas Vepstas <linasvepstas@...il.com>, david@...g.hm, Kyle Moffett <kyle@...fetthome.net>, Ben Goodger <goodgerster@...il.com>, Robert Hancock <hancockr@...w.ca>, linux-kernel@...r.kernel.org, "Jeffrey J. Kosowsky" <jeff@...owsky.org>, MentalMooMan <slashdot@...eshallam.info>, Travis Crump <pretzalz@...hhouse.org>, burdell@...ntheinter.net Subject: Re: Bug: Status/Summary of slashdot leap-second crash on new years 2008-2009 > > 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. mktime in the kernel has no knowledge of leap seconds whatsoever. Go read kernel/time.c > 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. All the kernel knows how to do is to slew time (in general) and to repeat or remove one second. It has no knowledge of leap seconds and it doesn't know how to convert between UTC/TAI/Unix Epoch etc -- 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