On Thu, Jun 13, 2019 at 05:31:09PM -0500, Dave Chiluk wrote:
> I was able to bisect this down to 53216e7 being the problematic commit,
> when using calls to setsockopt(... SO_LINGER ...) as the test metric.
Oh great, thank you for doing this!
> I used the number of calls to setsockopt with SO_LINGER in them using the
> following command.
> $ sudo timeout 60s strace -e setsockopt,close -p $(ps -lf -C haproxy | tail
> -n 1 | awk -e '{print $4}') 2>&1 | tee 1.9-${V} ; grep LINGER 1.9-${V} | wc
> -l
>
> 53216e7 = 1
> 81a15af6b = 69
>
> Interesting to note is that 1.8.17 only has roughly 17. I'll see if I can
> do a bisection for that tomorrow.
This is interesting because there is no equivalent commit in 1.8 so it
may be possible that we've created a bug long ago that triggers more
easily in certain situations.
> Hope that helps.
Of course it does :-)
Cheers,
Willy
