linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: 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>,
	syzkaller <syzkaller@googlegroups.com>, shuah <shuah@kernel.org>
Subject: Re: [Automated-testing] syzkaller reproducers
Date: Fri, 11 Oct 2019 13:11:07 -0600	[thread overview]
Message-ID: <b715f3d7-547f-9a43-dc41-2e46ec3bfd51@kernel.org> (raw)
In-Reply-To: <20191011180248.GA24089@rei.lan>

On 10/11/19 12:02 PM, Cyril Hrubis wrote:
> Hi!
>> 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?
> 
> You are suposed to run the run.sh script in the bin directory.

Yeah that does work.

Would be helpful to have usage instructions instead of failing. :)

> 
>> I did a build which worked. There are some errors due to sys/cdefs.h
>> missing.
> 
> That is because you are missing 32bit gcc and devel libs.
> 

Yeah. I didn't think about that.

thanks,
-- Shuah

  reply	other threads:[~2019-10-11 19:11 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 [this message]
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=b715f3d7-547f-9a43-dc41-2e46ec3bfd51@kernel.org \
    --to=shuah@kernel.org \
    --cc=automated-testing@yoctoproject.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=chrubis@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).