Re: Bug: Status/Summary of slashdot leap-second crash on new years2008-2009

[David Newall]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/