Amaury Denoyelle 0274286dd3 BUG/MAJOR: server: fix deadlock when changing maxconn via agent-check ... The server_parse_maxconn_change_request locks the server lock. However, this function can be called via agent-checks or lua code which already lock it. This bug has been introduced by the following commit : commit 79a88ba3d0 BUG/MAJOR: server: prevent deadlock when using 'set maxconn server' This commit tried to fix another deadlock with can occur because previoulsy server_parse_maxconn_change_request requires the server lock to be held. However, it may call internally process_srv_queue which also locks the server lock. The locking policy has thus been updated. The fix is functional for the CLI 'set maxconn' but fails to address the agent-check / lua counterparts. This new issue is fixed in two steps : - changes from the above commit have been reverted. This means that server_parse_maxconn_change_request must again be called with the server lock. - to counter the deadlock fixed by the above commit, process_srv_queue now takes an argument to render the server locking optional if the caller already held it. This is only used by server_parse_maxconn_change_request. The above commit was subject to backport up to 1.8. Thus this commit must be backported in every release where it is already present.		2021-06-22 11:39:20 +02:00
..
haproxy	BUG/MAJOR: server: fix deadlock when changing maxconn via agent-check	2021-06-22 11:39:20 +02:00
import	BUG/MEDIUM: ebtree: Invalid read when looking for dup entry	2021-05-18 19:26:21 +02:00