From: Cyril Hrubis <chrubis@suse.cz>
To: George Kennedy <george.kennedy@oracle.com>
Cc: Dmitry Vyukov <dvyukov@google.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: Tue, 15 Oct 2019 15:44:07 +0200 [thread overview]
Message-ID: <20191015134407.GA12523@rei.lan> (raw)
In-Reply-To: <62903a33-8ffc-56b6-de1a-539f10b5de2a@oracle.com>
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...
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-10-15 13:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 11:46 syzkaller reproducers dvyukov
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 [this message]
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
[not found] ` <cd301033-f152-4eeb-bce3-2d95f39a05fbn@googlegroups.com>
2022-05-12 18:05 ` Palash Oswal
2022-05-13 9:29 ` Dmitry Vyukov
2022-05-13 11:35 ` George Kennedy
2022-05-13 12:16 ` Dmitry Vyukov
2022-05-16 7:41 ` Dmitry Vyukov
2022-05-16 12:42 ` George Kennedy
2022-05-16 16:51 ` Shuah Khan
2022-05-17 9:12 ` Dmitry Vyukov
2019-10-08 16:35 ` George Kennedy
2019-10-08 12:37 ` [Automated-testing] " Richard Palethorpe
2019-10-08 12:37 ` Richard Palethorpe
2019-10-08 12:53 ` Dmitry Vyukov
2019-10-08 13:14 ` Richard Palethorpe
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=20191015134407.GA12523@rei.lan \
--to=chrubis@suse.cz \
--cc=automated-testing@yoctoproject.org \
--cc=boris.ostrovsky@oracle.com \
--cc=dhaval.giani@gmail.com \
--cc=dvyukov@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.