From: Dmitry Vyukov <email@example.com> To: firstname.lastname@example.org Cc: email@example.com, Shuah Khan <firstname.lastname@example.org>, "open list:KERNEL SELFTEST FRAMEWORK" <email@example.com>, firstname.lastname@example.org, syzkaller <email@example.com> Subject: Re: [Automated-testing] syzkaller reproducers Date: Tue, 8 Oct 2019 14:53:24 +0200 [thread overview] Message-ID: <CACT4Y+akZ4h9kN1Gg329-fKq-G=QeDdoFxW_Bp_r7+0sDsEfirstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On Tue, Oct 8, 2019 at 2:37 PM Richard Palethorpe <firstname.lastname@example.org> wrote: > > Hello, > > Dmitry Vyukov <email@example.com> writes: > > > Hi Shuah, > > > > We discussed collecting and uploading all syzkaller reproducers > > somewhere. You wanted to see how they look. I've uploaded all current > > reproducers here: > > https://github.com/dvyukov/syzkaller-repros > > Minimalistic build/run scripts are included. > > +some testing mailing lists too as this can be used as a test suite > > If you have any potential uses for this, you are welcome to use it. > > But then we probably need to find some more official and shared place > > for them than my private github. > > The test programs can also be bulk updated if necessary, because all > > of this is auto-generated. > > > > Thanks > > I discussed this a bit with Metan. We think it would be fairly trivial > to create an LTP wrapper for these. > > So we just create an LTP test which forks and execs one of these > reproducers then checks for kernel taints after the child completes or > is killed. It can take the reproducer path as an argument and we can > generate a runtest file with all the reproducers in that we are able to > compile. > > I imagine a lot of these reproducers will not work on older kernels, so > this would just be a best efforts basis. We would ignore any problems > during execution unless there is a kernel error. > > This should work with existing LTP runners with maybe a minor change or > two to building and configuration. > > I will start experimenting with this and post the results to the LTP > mailing list. Hi Richard, Sounds great! Yes, these are totally best effort. May also require some configs, etc. Also note that each should be run in a clean temp dir and with a timeout b/c some have an infinite loop.
next prev parent reply other threads:[~2019-10-08 12:53 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-08 11:46 Dmitry Vyukov 2019-10-08 12:16 ` Dmitry Vyukov 2019-10-08 15:00 ` shuah 2019-10-11 17:38 ` shuah 2019-10-11 18:02 ` [Automated-testing] " Cyril Hrubis 2019-10-11 19:11 ` shuah 2019-10-14 8:54 ` Cyril Hrubis 2019-10-14 11:19 ` Dmitry Vyukov 2019-10-15 13:04 ` George Kennedy 2019-10-15 13:44 ` Cyril Hrubis 2019-10-23 13:24 ` Dmitry Vyukov 2019-12-06 20:06 ` George Kennedy 2020-01-27 14:19 ` George Kennedy 2020-01-27 15:26 ` Dmitry Vyukov 2020-01-27 17:06 ` George Kennedy 2020-03-03 8:45 ` Dmitry Vyukov 2020-03-03 13:46 ` George Kennedy 2020-03-13 15:59 ` shuah 2019-10-08 16:35 ` George Kennedy 2019-10-08 12:37 ` [Automated-testing] " Richard Palethorpe 2019-10-08 12:53 ` Dmitry Vyukov [this message] 2019-10-08 13:14 ` Richard Palethorpe 2019-10-08 13:22 ` Dmitry Vyukov 2019-10-10 14:27 ` Cyril Hrubis 2019-10-10 14:30 ` Dmitry Vyukov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CACT4Y+akZ4h9kN1Gg329-fKq-G=QeDdoFxW_Bp_r7+0sDsEfirstname.lastname@example.org' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [Automated-testing] syzkaller reproducers' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).