Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753268AbbK2Og7 (ORCPT ); Sun, 29 Nov 2015 09:36:59 -0500 Received: from mail-wm0-f45.google.com ([74.125.82.45]:33659 "EHLO mail-wm0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753216AbbK2Og4 (ORCPT ); Sun, 29 Nov 2015 09:36:56 -0500 MIME-Version: 1.0 In-Reply-To: <5659030C.1070009@oracle.com> References: <56587467.8050102@oracle.com> <1448647077.6523.33.camel@tiscali.nl> <56589DD9.2060508@oracle.com> <1448670517.6523.67.camel@tiscali.nl> <56590159.4080404@hurleysoftware.com> <5659030C.1070009@oracle.com> From: Dmitry Vyukov Date: Sun, 29 Nov 2015 15:36:35 +0100 Message-ID: Subject: Re: gigaset: freeing an active object To: Sasha Levin Cc: Peter Hurley , Paul Bolle , isdn@linux-pingi.de, David Miller , tilman@imap.cc, gigaset307x-common@lists.sourceforge.net, LKML , "netdev@vger.kernel.org" , syzkaller Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1349 Lines: 28 On Sat, Nov 28, 2015 at 2:27 AM, Sasha Levin wrote: > On 11/27/2015 08:20 PM, Peter Hurley wrote: >> It would really help if you included the syzkaller-generated applet with >> the bug reports; state previously established by the applet can be >> crucial in understanding why the call stack looks the way it does. >> >> Also, every generated applet that triggers a report should become >> a future regression test; I'm collecting the ones pertinent to tty/serial/ >> ldisc (so that includes this one; if you could send me the x25 one too >> would be great). > > I went in to look for the 'crashers' that I thought are generated when > syzkaller manages to crash a kernel, but none appear for me. > > Dmitry, is there magic required to generate those? There is a little bit of magic, but mostly hard muscle labor. I've outlined how I create reproducers here: https://github.com/google/syzkaller/wiki/Crash-reproducer-programs The description is not super detailed, but should be give you some clue. Ideally it is all automated, but somebody needs to write some code for that... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/