From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933527AbdKBOam (ORCPT ); Thu, 2 Nov 2017 10:30:42 -0400 Received: from mail-pg0-f66.google.com ([74.125.83.66]:53989 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933020AbdKBOak (ORCPT ); Thu, 2 Nov 2017 10:30:40 -0400 X-Google-Smtp-Source: ABhQp+SlgB8wx9GYQ15yUzyk1oo79IAdxx52IVxskC4VJ5qD+fz/ZBEcnu1KIE85mSJ0hvYq3FPnZQ== Message-ID: <1509633037.2849.5.camel@edumazet-glaptop3.roam.corp.google.com> Subject: Re: WARNING: at net/core/stream.c:204 From: Eric Dumazet To: Shankara Pailoor Cc: David Miller , Linux Kernel Network Developers , LKML , acme@conectiva.com.br, alan@lxorguk.ukuu.org.uk, Andrew Zhu Aday , syzkaller Date: Thu, 02 Nov 2017 07:30:37 -0700 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.