Re: v1.9.x segfault on LIST_DEL(>wait_queue)

2019-04-17 Thread Willy Tarreau
Hi William, On Wed, Apr 17, 2019 at 07:29:49AM +, William Dauchy wrote: > Hello Willy, > > On Thu, Apr 11, 2019 at 11:34:52AM +0200, Willy Tarreau wrote: > > With this said, we've got no negative feedback on the patch above after > > one month and a half, which likely is a good indication

Re: v1.9.x segfault on LIST_DEL(>wait_queue)

2019-04-17 Thread William Dauchy
Hello Willy, On Thu, Apr 11, 2019 at 11:34:52AM +0200, Willy Tarreau wrote: > With this said, we've got no negative feedback on the patch above after > one month and a half, which likely is a good indication that we should > now backport it (carefully as mentionned in the commit message). Based

Re: v1.9.x segfault on LIST_DEL(>wait_queue)

2019-04-11 Thread William Dauchy
Hi Willy, On Thu, Apr 11, 2019 at 11:34:52AM +0200, Willy Tarreau wrote: > Unfortunately this one looks different. It dies when it is stopping > (see deinit, unbind*, ...), are you sure it's not the previous process > when you're performing a reload ? Note that it *could* possibly still > be the

Re: v1.9.x segfault on LIST_DEL(>wait_queue)

2019-04-11 Thread Willy Tarreau
Hi William, On Wed, Apr 10, 2019 at 06:00:28PM +, William Dauchy wrote: > Hello, > > We are seeing a quite regular segfault when haproxy v1.9 joins our cluster > and almost immediately crash with: > > #0 0x55b66f75c825 in do_unbind_listener > (listener=listener@entry=0x55b67206dcb0,

v1.9.x segfault on LIST_DEL(>wait_queue)

2019-04-10 Thread William Dauchy
Hello, We are seeing a quite regular segfault when haproxy v1.9 joins our cluster and almost immediately crash with: #0 0x55b66f75c825 in do_unbind_listener (listener=listener@entry=0x55b67206dcb0, do_close=do_close@entry=1) at src/listener.c:328 328