On Tue, Jun 21, 2022 at 10:17 AM Peter Foley wrote:
> The upstream fixes in
> https://gitlab.freedesktop.org/slirp/libslirp/-/commit/6489ebbc691f5d97221ad154d570a231e30fb369
> and
> https://gitlab.freedesktop.org/slirp/libslirp/-/commit/cc20d9ac578aec5502dcb26557765d3e9433cb26
> resolved the fail
The upstream fixes in
https://gitlab.freedesktop.org/slirp/libslirp/-/commit/6489ebbc691f5d97221ad154d570a231e30fb369
and
https://gitlab.freedesktop.org/slirp/libslirp/-/commit/cc20d9ac578aec5502dcb26557765d3e9433cb26
resolved the failure we were seeing in our internal test-case.
Thanks!
On Tue, J
On Fri, Jun 17, 2022 at 7:37 AM Alexander Bulekov wrote:
> On 220617 1217, Thomas Huth wrote:
> > On 16/06/2022 21.03, Alexander Bulekov wrote:
> > > On 220616 0930, Patrick Venture wrote:
> > > > On Thu, Jun 16, 2022 at 6:31 AM Alexander Bulekov
> wrote:
> > > >
> > > > > Is this an --enable-sa
On 220617 1217, Thomas Huth wrote:
> On 16/06/2022 21.03, Alexander Bulekov wrote:
> > On 220616 0930, Patrick Venture wrote:
> > > On Thu, Jun 16, 2022 at 6:31 AM Alexander Bulekov wrote:
> > >
> > > > Is this an --enable-sanitizers build? The virtual-device fuzzer catches
> > > >
> > >
> > >
On 16/06/2022 21.03, Alexander Bulekov wrote:
On 220616 0930, Patrick Venture wrote:
On Thu, Jun 16, 2022 at 6:31 AM Alexander Bulekov wrote:
Is this an --enable-sanitizers build? The virtual-device fuzzer catches
Yeah - it should be reproducible with a sanitizers build from HEAD -- I can
On 220616 0930, Patrick Venture wrote:
> On Thu, Jun 16, 2022 at 6:31 AM Alexander Bulekov wrote:
>
> > Is this an --enable-sanitizers build? The virtual-device fuzzer catches
> >
>
> Yeah - it should be reproducible with a sanitizers build from HEAD -- I can
> try to get a manual instance going
On Thu, Jun 16, 2022 at 6:31 AM Alexander Bulekov wrote:
> Is this an --enable-sanitizers build? The virtual-device fuzzer catches
>
Yeah - it should be reproducible with a sanitizers build from HEAD -- I can
try to get a manual instance going again without automation to try and
reproduce it. W
Is this an --enable-sanitizers build? The virtual-device fuzzer catches
these periodically while fuzzing network-devices. However I don't think
OSS-Fuzz creates reports for them for some reason. I can create qtest
reproducers, if that is useful.
-Alex
On 220615 0942, Patrick Venture wrote:
> Hey
Hey - I wanted to ask if someone else has seen this or has suggestions on
how to fix it in libslirp / qemu.
libslirp version: 3ad1710a96678fe79066b1469cead4058713a1d9
The blow is line:
https://gitlab.freedesktop.org/slirp/libslirp/-/blob/master/src/tcp_input.c#L310
I0614 13:44:44.3040872040
