Hello, What is the risk to trigger this bug in real life ? How to avoid it before the next haproxy release ? In my setup haproxy 2.1.5 has threads enabled by default (Debian Buster backports).
Le 02/06/2020 à 19:28, William Dauchy a écrit : > On Tue, Jun 2, 2020 at 12:13 PM William Dauchy <wdau...@gmail.com> wrote: >> it seems like I broke something with this commit, but I did not have >> it in v2.2 > small followup: > Sorry for that one, the backport was not exactly as I thought, and so > no test were done before release outside of 2.2 branch: > - a small mistake in index within a loop > - more importantly, srv->idle_conns and srv->safe_conns are not > thread-safe list in 2.0 and 2.1 > > I choose to revert the changes < 2.2 -- Best regards, Artur
