BUG/MINOR: task: always reset a new tasklet's call date
The tasklet's call date was not reset, so if profiling was enabled while
some tasklets were in the run queue, their initial random value could be
used to preload a bogus initial latency value into the task profiling bin.
Let's just zero the initial value.
This should be backported to 2.4 as it was brought with initial commit
b2285de04 ("MINOR: tasks: also compute the tasklet latency when DEBUG_TASK
is set"). The impact is very low though.
(cherry picked from commit f27acd961e9b4291f80bc54100e57969ec4372ec)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit c94b84c6ba1f7900aa66f21e570a3b900f8ad967)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 38299c0951f31b94bfe15a16626bc384e0d70e52)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
1 file changed