d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix an extreme edge case in leap second handling. We need to call

Browse Source 
ntp_update_second twice when we have a large step in case that step
goes across a scheduled leap second.  The only way this could happen
would be if we didn't call tc_windup over the end of day on the day of
a leap second, which would only happen if timeouts were delayed for
seconds.  While it is an edge case, it is an important one to get
right for my employer.

Sponsored by: Timing Solutions Corporation
This commit is contained in:
imp 2003-08-20 05:34:27 +00:00
parent dd5e41ad29
commit ef7e40c451
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
sys/kern/kern_tc.c
View File

@ -406,15 +406,17 @@ tc_windup(void)
* iterates once, but in extreme situations it might keep NTP sane
* if timeouts are not run for several seconds. At boot, the
* time step can be large when the TOD hardware has been read, so
* on really large steps, we call ntp_update_second only once.
* on really large steps, we call ntp_update_second only twice.
* We need to call it twice in case we missed a leap second.
*/
for (i = bt.sec - tho->th_microtime.tv_sec; i > 0; i--) {
i = bt.sec - tho->th_microtime.tv_sec;
if (i > LARGE_STEP)
i = 2;
for (; i > 0; i--) {
t = bt.sec;
ntp_update_second(&th->th_adjustment, &bt.sec);
if (bt.sec != t)
boottimebin.sec += bt.sec - t;
if (i > LARGE_STEP)
break;
}
/* Now is a good time to change timecounters. */