Re: haproxy-1.9 sanitizers finding

2019-05-09 Thread Willy Tarreau
On Wed, May 08, 2019 at 01:04:36PM +0500,  ??? wrote:
> I would like to run sanitizers before new 1.9 release is out

OK I've pushed 1.9-master with the last pending fixes. I guess it will
break on libressl, but it passes the sanitize=address (except the one
you already reported in libssl.so.1).

Willy



Re: haproxy-1.9 sanitizers finding

2019-05-08 Thread Илья Шипицин
I would like to run sanitizers before new 1.9 release is out

On Wed, May 8, 2019, 10:54 AM Willy Tarreau  wrote:

> Hi Ilya,
>
> On Tue, May 07, 2019 at 11:47:54AM +0500,  ??? wrote:
> > Hello,
> >
> > when running regtests against 1.9 branch there are findings (not seen in
> > master branch)
> >
> > ***  h10.0
> > debug|=
> > ***  h10.0 debug|==16493==ERROR: AddressSanitizer:
> heap-use-after-free
> > on address 0x61903c95 at pc 0x006ca207 bp 0x7ffd92124b60 sp
> > 0x7ffd92124b50
> > ***  h10.0 debug|WRITE of size 1 at 0x61903c95 thread T0
> > ***  h10.0 debug|#0 0x6ca206 in update_log_hdr src/log.c:1260
> > ***  h10.0 debug|#1 0x6ca206 in __send_log src/log.c:1445
> > ***  h10.0 debug|#2 0x6ca48a in send_log src/log.c:1323
> (...)
>
> OK these are the same that you reported on master which is fixed there
> and not backported yet. It should eventually get backported ;-)
>
> Thanks,
> Willy
>


Re: haproxy-1.9 sanitizers finding

2019-05-07 Thread Willy Tarreau
Hi Ilya,

On Tue, May 07, 2019 at 11:47:54AM +0500,  ??? wrote:
> Hello,
> 
> when running regtests against 1.9 branch there are findings (not seen in
> master branch)
> 
> ***  h10.0
> debug|=
> ***  h10.0 debug|==16493==ERROR: AddressSanitizer: heap-use-after-free
> on address 0x61903c95 at pc 0x006ca207 bp 0x7ffd92124b60 sp
> 0x7ffd92124b50
> ***  h10.0 debug|WRITE of size 1 at 0x61903c95 thread T0
> ***  h10.0 debug|#0 0x6ca206 in update_log_hdr src/log.c:1260
> ***  h10.0 debug|#1 0x6ca206 in __send_log src/log.c:1445
> ***  h10.0 debug|#2 0x6ca48a in send_log src/log.c:1323
(...)

OK these are the same that you reported on master which is fixed there
and not backported yet. It should eventually get backported ;-)

Thanks,
Willy