tree 9c323e34face1f4b0bedcfb7720aa5c559027d4f
parent 8e9732605d789ad577f23d111bff1f4a3c3f252d
author Willy Tarreau <w@1wt.eu> 1726156737 +0200
committer Christopher Faulet <cfaulet@haproxy.com> 1726559599 +0200

BUG/MINOR: clock: make time jump corrections a bit more accurate

Since commit e8b1ad4c2b ("BUG/MEDIUM: clock: also update the date offset
on time jumps") we try to update the now_offet based on the last known
valid date. But if it's off compared to the global_now_ns date shared
by other threads, we'll get the time off a little bit. When this happens,
we should consider the most recent of these dates so that if the global
date was already known to be more recent, we should use it and stick to
it. This will avoid setting too large an offset that could in turn provoke
a larger jump on another thread.

This is related to issue GH #2704.

This can be backported to other branches having the patch above.

(cherry picked from commit af48e4cc6b315cadb80d6980586af5c3c8368826)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 6eac661927d5eea2a782796c8f6be75a4919b5ab)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 7ff68ebc77ece11e7be7633b9ec4922f072104a4)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>