Re: WARNING: at net/core/stream.c:204

2017-11-02 Thread Eric Dumazet
On Thu, 2017-11-02 at 08:36 -0400, Shankara Pailoor wrote: > Hi, > > We encountered the following warning when fuzzing with Syzkaller on > Linux 4.14-rc4. Syzkaller was able to isolate the sequence of calls > which caused the bug but couldn't create a C program that could > regularly trigger it.

Re: WARNING: at net/core/stream.c:204

2017-11-02 Thread Eric Dumazet
On Thu, 2017-11-02 at 08:36 -0400, Shankara Pailoor wrote: > Hi, > > We encountered the following warning when fuzzing with Syzkaller on > Linux 4.14-rc4. Syzkaller was able to isolate the sequence of calls > which caused the bug but couldn't create a C program that could > regularly trigger it.

WARNING: at net/core/stream.c:204

2017-11-02 Thread Shankara Pailoor
Hi, We encountered the following warning when fuzzing with Syzkaller on Linux 4.14-rc4. Syzkaller was able to isolate the sequence of calls which caused the bug but couldn't create a C program that could regularly trigger it. Here are the logs from the reproducer attempts:

WARNING: at net/core/stream.c:204

2017-11-02 Thread Shankara Pailoor
Hi, We encountered the following warning when fuzzing with Syzkaller on Linux 4.14-rc4. Syzkaller was able to isolate the sequence of calls which caused the bug but couldn't create a C program that could regularly trigger it. Here are the logs from the reproducer attempts: