Re: time(1) reporting corrupted system time

[mlelstv%serpens.de@localhost (Michael van Elst)]

gson%gson.org@localhost (Andreas Gustafsson) writes:

>My efforts are hampered by time(1) reporting corrupted system times on
>certain past versions of -current:

>  2017.01.01.03.06.06/build_8.log:     3562.32 real     15806.10 user      4893.62 sys
>  2018.05.21.10.28.13/build_8.log:     4250.22 real     16835.23 user 608742554440425.55 sys
>  2019.01.30.20.20.36/build_8.log:     4228.25 real     16801.48 user 700976274808841.24 sys
>  2019.09.27.08.57.12/build_8.log:     4488.49 real     16670.79 user      9279.25 sys

>Does anyone happen to know which commits caused and/or fixed this?
>This information could save me a couple of days of bisection run time.

First there was a change to precent that user/system time are decreasing
in kern-resource.c 1.180. But it shouldn't be related to negative numbers.

Additionally a possible underflow of user/system time was fixed in
kern_resource.c 1.182. This prevents negative numbers, but IIRC this
would only happen for very small values, not when values already
accumulated to a few thousand seconds.




-- 
-- 
                                Michael van Elst
Internet: mlelstv%serpens.de@localhost
                                "A potential Snark may lurk in every tree."