From: shuah <shuah@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
automated-testing@yoctoproject.org, kernelci@groups.io,
George Kennedy <george.kennedy@oracle.com>,
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>
Cc: syzkaller <syzkaller@googlegroups.com>, shuah <shuah@kernel.org>
Subject: Re: syzkaller reproducers
Date: Fri, 11 Oct 2019 11:38:07 -0600 [thread overview]
Message-ID: <226099bc-9763-3a73-e26a-b292f601494c@kernel.org> (raw)
In-Reply-To: <876a2abe-41ab-5819-4ae8-ad26186d0d1c@kernel.org>
On 10/8/19 9:00 AM, shuah wrote:
> On 10/8/19 6:16 AM, Dmitry Vyukov wrote:
>> On Tue, Oct 8, 2019 at 1:46 PM Dmitry Vyukov <dvyukov@google.com> wrote:
>>>
>>> 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
>>
>> +more people who expressed interest in the test suite before
>>
>
> Thanks for putting this together. I am going to create a repo on
> kernel.org t host these and pull your private git content in.
>
> I will work on it this week and set things up.
>
Playing with the git getting ready to host it on kernel.org git repo.
Build worked fine and I can't get the run.sh to work.
I expected it to run what is in
syzkaller-repros/bin
It doesn't seem to do that. Looks like it wants to build. Here is what
I see. What am I doing wrong? I did a build which worked. There are some
errors due to sys/cdefs.h missing.
++ for f in *
+++ pwd
++ bin=/mnt/data/lkml/syzkaller-repros/bin
+++ mktemp -d
++ dir=/tmp/tmp.S8CjM8muRj
++ cd /tmp/tmp.S8CjM8muRj
++ timeout -s KILL 3 /mnt/data/lkml/syzkaller-repros/bin
timeout: failed to run command ‘/mnt/data/lkml/syzkaller-repros/bin’:
Permission denied
++ rm -rf /tmp/tmp.S8CjM8muRj
++ for f in *
+++ pwd
++ bin=/mnt/data/lkml/syzkaller-repros/build.sh
+++ mktemp -d
++ dir=/tmp/tmp.zAVygWdpkt
++ cd /tmp/tmp.zAVygWdpkt
++ timeout -s KILL 3 /mnt/data/lkml/syzkaller-repros/build.sh
linux/*.c
grep: linux/*.c: No such file or directory
gcc: error: linux/*.c: No such file or directory
gcc: fatal error: no input files
compilation terminated.
++ rm -rf /tmp/tmp.zAVygWdpkt
++ for f in *
+++ pwd
++ bin=/mnt/data/lkml/syzkaller-repros/LICENSE
+++ mktemp -d
++ dir=/tmp/tmp.hhcvgOc8RA
++ cd /tmp/tmp.hhcvgOc8RA
++ timeout -s KILL 3 /mnt/data/lkml/syzkaller-repros/LICENSE
timeout: failed to run command
‘/mnt/data/lkml/syzkaller-repros/LICENSE’: Permission denied
++ rm -rf /tmp/tmp.hhcvgOc8RA
++ for f in *
+++ pwd
++ bin=/mnt/data/lkml/syzkaller-repros/linux
+++ mktemp -d
++ dir=/tmp/tmp.sM5UO7BHRB
++ cd /tmp/tmp.sM5UO7BHRB
++ timeout -s KILL 3 /mnt/data/lkml/syzkaller-repros/linux
timeout: failed to run command ‘/mnt/data/lkml/syzkaller-repros/linux’:
Permission denied
++ rm -rf /tmp/tmp.sM5UO7BHRB
++ for f in *
+++ pwd
++ bin=/mnt/data/lkml/syzkaller-repros/README.md
+++ mktemp -d
++ dir=/tmp/tmp.4Kkrs6iLP5
++ cd /tmp/tmp.4Kkrs6iLP5
++ timeout -s KILL 3 /mnt/data/lkml/syzkaller-repros/README.md
timeout: failed to run command
‘/mnt/data/lkml/syzkaller-repros/README.md’: Permission denied
++ rm -rf /tmp/tmp.4Kkrs6iLP5
++ for f in *
+++ pwd
++ bin=/mnt/data/lkml/syzkaller-repros/run.sh
+++ mktemp -d
++ dir=/tmp/tmp.YFx5WEOvJn
++ cd /tmp/tmp.YFx5WEOvJn
++ timeout -s KILL 3 /mnt/data/lkml/syzkaller-repros/run.sh
+ pwd
+ bin=/tmp/tmp.YFx5WEOvJn/*
+ mktemp -d
+ dir=/tmp/tmp.qD4i4g9qYR
+ cd /tmp/tmp.qD4i4g9qYR
+ timeout -s KILL 3 /tmp/tmp.YFx5WEOvJn/*
timeout: failed to run command ‘/tmp/tmp.YFx5WEOvJn/*’: No such file or
directory
+ rm -rf /tmp/tmp.qD4i4g9qYR
++ rm -rf /tmp/tmp.YFx5WEOvJn
thanks,
-- Shuah
next prev parent reply other threads:[~2019-10-11 17:38 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 [this message]
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
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=226099bc-9763-3a73-e26a-b292f601494c@kernel.org \
--to=shuah@kernel.org \
--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=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