| |||||||||||||
Re: [PATCH 0/2][RFC] Potential fix for leapsecond caused futex issue (v2)Re: [PATCH 0/2][RFC] Potential fix for leapsecond caused futex issue (v2)Posted Jul 2, 2012 17:24 UTC (Mon) by Jonno (subscriber, #49613)In reply to: Re: [PATCH 0/2][RFC] Potential fix for leapsecond caused futex issue (v2) by lindi Parent article: Re: [PATCH 0/2][RFC] Potential fix for leapsecond caused futex issue (v2)
Yes, that is the correct behaviour of gettimeofday().
However, there was some internal kernel code that expected to be informed when the time of day and elapsed time wasn't continuous (done by calling clock_was_set()). The code for settimeofday() got this right, but the clock_was_set() call was missing from the leap second introducing code, leading to some trouble I don't really understand.
(Log in to post comments)
|
|||||||||||||