linux-kernel - Re: WARNING: at net/core/stream.c:204

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 02 Nov 2017 07:30:37 -0700
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Shankara Pailoor <sp3485@...umbia.edu>
Cc:     David Miller <davem@...emloft.net>,
        Linux Kernel Network Developers <netdev@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>, acme@...ectiva.com.br,
        alan@...rguk.ukuu.org.uk,
        Andrew Zhu Aday <andrew.aday@...umbia.edu>,
        syzkaller <syzkaller@...glegroups.com>
Subject: Re: WARNING: at net/core/stream.c:204

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.
> 
> 
> Here are the logs from the reproducer attempts: https://pastebin.com/QWQZK6hW
> 
> Here is the original stack trace: https://pastebin.com/7L4WciRr

Sorry, we are flooded by such reports, so you have to give the exact
details, and find a C repro.

A bonus if you actually send a kernel patch, of course.

Thanks.