[Automated-testing] syzkaller reproducers

George Kennedy george.kennedy at oracle.com
Tue Oct 15 06:04:01 PDT 2019



On 10/14/2019 7:19 AM, Dmitry Vyukov wrote:
> On Mon, Oct 14, 2019 at 10:54 AM Cyril Hrubis <chrubis at suse.cz> wrote:
>> Hi!
>>>> 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 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.

George




More information about the automated-testing mailing list