From: Dmitry Vyukov <dvyukov@google.com>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Shuah Khan <shuah@kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
automated-testing@yoctoproject.org, kernelci@groups.io,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: [Automated-testing] syzkaller reproducers
Date: Thu, 10 Oct 2019 16:30:27 +0200 [thread overview]
Message-ID: <CACT4Y+ZiC_m-U1+Zxs3hhOM7j2seKKjX=H9eabUAGCctm1+8OQ@mail.gmail.com> (raw)
In-Reply-To: <20191010142744.GA10083@rei.lan>
On Thu, Oct 10, 2019 at 4:27 PM Cyril Hrubis <chrubis@suse.cz> wrote:
>
> Hi!
> > 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.
>
> What is the reason behind statically linking the reproducers?
>
> The difference between static and dynamic binary is a bit less than 4MB,
> which gives difference of several gigabytes for the whole repo. This
> amount of binary data would complicate and slow down any CI
> significantly...
Simply being able to run programs on a different machine. Dynamic
binaries generally don't run on a different linux machine. If you can
build dynamic binaries so that they run on test machine, feel free to
drop -static.
prev parent reply other threads:[~2019-10-10 14:30 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
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 [this message]
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+ZiC_m-U1+Zxs3hhOM7j2seKKjX=H9eabUAGCctm1+8OQ@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=automated-testing@yoctoproject.org \
--cc=chrubis@suse.cz \
--cc=kernelci@groups.io \
--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).