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.
I would guess that these reproducers are product of countless hours of fuzzing, so it's about to be expected...