[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5659030C.1070009@oracle.com>
Date: Fri, 27 Nov 2015 20:27:40 -0500
From: Sasha Levin <sasha.levin@...cle.com>
To: Peter Hurley <peter@...leysoftware.com>,
Paul Bolle <pebolle@...cali.nl>,
Dmitry Vyukov <dvyukov@...gle.com>
Cc: isdn@...ux-pingi.de, davem@...emloft.net, tilman@...p.cc,
gigaset307x-common@...ts.sourceforge.net,
LKML <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: gigaset: freeing an active object
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?
Thanks,
Sasha
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists