| 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
| ||
|
Message-ID: <495F0672.6020708@davidnewall.com> Date: Sat, 03 Jan 2009 17:02:18 +1030 From: David Newall <davidn@...idnewall.com> To: Robert Hancock <hancockr@...w.ca> CC: linux-kernel@...r.kernel.org, linasvepstas@...il.com, "Jeffrey J. Kosowsky" <jeff@...owsky.org>, MentalMooMan <slashdot@...eshallam.info>, Travis Crump <pretzalz@...hhouse.org>, Goodgerster <goodgerster@...il.com>, burdell@...ntheinter.net Subject: Re: Bug: Status/Summary of slashdot leap-second crash on new years 2008-2009 Robert Hancock wrote: > Diego Calleja wrote: >> How could I create a test case that reproduces what ntp does? Just add >> a second? > > I'd think that setting the clock to just before midnight on Dec.31 and > using the adjtimex syscall to set the TIME_INS state on the clock, > then waiting until midnight rolls around would be a reasonable test.. I don't understand this idea, nor the patch for the problem. I don't see why adding a leap second would impact the kernel in any way. Shouldn't this be a simple zoneinfo change, whereby the last two seconds of the year (in each timezone) both map to 31dec2008 23:59:59? That's the way the change has worked in the real world. Why would ntp or the kernel be involved? -- 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