syz-manager: re-smash a subset of the corpus on restart

We smash the program only once after we add it to the corpus, but
it can be that
1) It did not finish before the instance was restarted.
2) The fuzzing algorithms have become smarter over time.
3) That kernel code has changed over time.

It would be best to track it in pkg/db, but until it's capable
of that, let's just re-smash some corpus subset on each
syz-manager restart.

0 files changed, 0 insertions, 0 deletions