Re: [Automated-testing] syzkaller reproducers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 10/14/2019 7:19 AM, Dmitry Vyukov wrote:
On Mon, Oct 14, 2019 at 10:54 AM Cyril Hrubis <chrubis@xxxxxxx> 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





[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux