Greg Troxel
2015-08-05 16:27:40 UTC
Some codes in sys/net* use time_second to
manage time periods such as cache expirations.
However, time_second doesn't increase monotonically
and can leap by say settimeofday(2) according to
time_second(9). We should use time_uptime
instead of it to avoid such time leaps.
http://www.netbsd.org/~ozaki-r/use-time_uptime.diff
Generally this sounds sensible. One thing to consider is whether thismanage time periods such as cache expirations.
However, time_second doesn't increase monotonically
and can leap by say settimeofday(2) according to
time_second(9). We should use time_uptime
instead of it to avoid such time leaps.
http://www.netbsd.org/~ozaki-r/use-time_uptime.diff
change results in leaking uptime to hosts over the network. (That could
be used to help identify roving hosts.)