On Sat, Nov 28, 2015 at 2:27 AM, Sasha Levin <sasha.le...@oracle.com> 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
