Christopher Faulet 8f100427c4 BUG/MEDIUM: tcpcheck: Don't destroy connection in the wake callback context ... When a tcpcheck ruleset uses multiple connections, the existing one must be closed and destroyed before openning the new one. This part is handled in the tcpcheck_main() function, when called from the wake callback function (wake_srv_chk). But it is indeed a problem, because this function may be called from the mux layer. This means a mux may call the wake callback function of the data layer, which may release the connection and the mux. It is easy to see how it is hazardous. And actually, depending on the scheduling, it leads to crashes. Thus, we must avoid to release the connection in the wake callback context, and move this part in the check's process function instead. To do so, we rely on the CHK_ST_CLOSE_CONN flags. When a connection must be replaced by a new one, this flag is set on the check, in tcpcheck_main() function, and the check's task is woken up. Then, the connection is really closed in process_chk_conn() function. This patch must be backported as far as 2.2, with some adaptations however because the code is not exactly the same.		2021-01-21 15:21:12 +01:00
..
haproxy	BUG/MEDIUM: tcpcheck: Don't destroy connection in the wake callback context	2021-01-21 15:21:12 +01:00
import	CLEANUP: Fix spelling errors in comments	2021-01-08 14:56:32 +01:00