From: Dmitry Vyukov <dvyukov@google.com>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: George Kennedy <george.kennedy@oracle.com>,
shuah <shuah@kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
automated-testing@yoctoproject.org, kernelci@groups.io,
Dhaval Giani <dhaval.giani@gmail.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Jan Setje-Eilers <jan.setjeeilers@oracle.com>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: [Automated-testing] syzkaller reproducers
Date: Wed, 23 Oct 2019 15:24:17 +0200 [thread overview]
Message-ID: <CACT4Y+azc_6aoEf4GaVFwwZgLp9QcCk3jJB-spM9s5BUB8Gxqg@mail.gmail.com> (raw)
In-Reply-To: <20191015134407.GA12523@rei.lan>
On Tue, Oct 15, 2019 at 3:44 PM Cyril Hrubis <chrubis@suse.cz> wrote:
>
> Hi!
> > >> I do not think that these scripts are ever supposed to be the used in
> > >> production testing, you need much more than this to produce results
> > >> reliably. I would expect that they are supposed to be a form of very
> > >> minimal documentation.
> > > Yes, I just added them as quick hints: some repros are 32-bits; each
> > > needs a new dir; some external timeout is needed for each test.
> > Thank you again for the collection of repro C programs!
> >
> > Hitting a lot more crashes with the collection of repro C programs than
> > in all the hours of running Syzkaller. Wonder why? Any idea? This is
> > with the same kernel and VM that Syzkaller is run on.
>
> I would guess that these reproducers are product of countless hours of
> fuzzing, so it's about to be expected...
Probably. Hard to say.
If you used KCOV, KCOV_ENABLE_COMPARISONS, KASAN, LOCKDEP,
FAULT_INJECTION, all other debugging configs, compat instance and some
required image/cmdline features, then the only reason for difference
that I see is indeed longer fuzzing time.
next prev parent reply other threads:[~2019-10-23 13:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 11:46 syzkaller reproducers 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 [this message]
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
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+azc_6aoEf4GaVFwwZgLp9QcCk3jJB-spM9s5BUB8Gxqg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=automated-testing@yoctoproject.org \
--cc=boris.ostrovsky@oracle.com \
--cc=chrubis@suse.cz \
--cc=dhaval.giani@gmail.com \
--cc=george.kennedy@oracle.com \
--cc=jan.setjeeilers@oracle.com \
--cc=kernelci@groups.io \
--cc=konrad.wilk@oracle.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=syzkaller@googlegroups.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).