BUG/MEDIUM: resolvers: Use tick_first() to update the resolvers task timeout
In resolv_update_resolvers_timeout(), the resolvers task timeout is updated by checking running and waiting resolutions. However, to find the next wakeup date, MIN() operator is used to compare ticks. Ticks must never be compared with such operators, tick helper functions must be used, to properly handled TICK_ETERNITY value. In this case, tick_first() must be used instead of MIN(). It is an old bug but it is pretty visible since the commitfdecaf6ae4
("BUG/MINOR: resolvers: do not run the timeout task when there's no resolution"). Because of this bug, the resolvers task timeout may be set to TICK_ETERNITY, stopping periodic resolutions. This patch should solve the issue #1962. It must be backported to all stable versions. (cherry picked from commit819d48b14e
) Signed-off-by: Christopher Faulet <cfaulet@haproxy.com> (cherry picked from commit d94ca04f965fd5a2ad7ee500b8bbf46acd722206) Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
This commit is contained in:
@ -291,11 +291,11 @@ static void resolv_update_resolvers_timeout(struct resolvers *resolvers)
|
||||
next = tick_add(now_ms, resolvers->timeout.resolve);
|
||||
if (!LIST_ISEMPTY(&resolvers->resolutions.curr)) {
|
||||
res = LIST_NEXT(&resolvers->resolutions.curr, struct resolv_resolution *, list);
|
||||
next = MIN(next, tick_add(res->last_query, resolvers->timeout.retry));
|
||||
next = tick_first(next, tick_add(res->last_query, resolvers->timeout.retry));
|
||||
}
|
||||
|
||||
list_for_each_entry(res, &resolvers->resolutions.wait, list)
|
||||
next = MIN(next, tick_add(res->last_resolution, resolv_resolution_timeout(res)));
|
||||
next = tick_first(next, tick_add(res->last_resolution, resolv_resolution_timeout(res)));
|
||||
|
||||
resolvers->t->expire = next;
|
||||
task_queue(resolvers->t);
|
||||
|
Reference in New Issue
Block a user