| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Copy everything into the build context.
Add a .dockerignore file to avoid copying the definitely unnecessary
files and folders.
Check copyrights presence in Dockerfiles.
|
| |
|
|
| |
Collect trace logs and make them accessible via the web UI.
|
| |
|
|
|
|
|
|
| |
Instead of a predefined set of manually written syz-manager configs,
construct it dynamically from different bits.
During triage, select not just one, but all matching fuzzer
configurations and then merge them together.
|
| |
|
|
|
|
| |
3G is not enough for kernels with KMSAN.
Slightly decrease the number of used VMs to fit into the available
CPUs/RAM.
|
| |
|
|
|
|
| |
If a boot test step failed and we don't report the finding to the
dashboard, print the report/output to the console to facilitate
debugging.
|
| |
|
|
|
| |
Our base configs have 4 VMs, but we don't need that many for the boot
test.
|
| |
|
|
|
| |
For some reason, it does not download the newer toolchain versions
automatically.
|
| |
|
|
|
|
| |
Retry the boot test up to 3 times before letting it fail and reporting
the failure as a finding. That should make sure there are fewer false
positives amoung the "boot error" and "test error" bugs.
|
| |
|
|
|
|
|
|
|
| |
Accept IMAGE_PREFIX and IMAGE_TAG parameters that allow to reuse the
Makefile and a lot of k8s configurations both for local and prod
environments.
Refactor Makefile: define build-* and push-* rules, use templates to
avoid repetition.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Provide an API to set up the reporting of finished sessions for which
syz-cluster collected reportable findings.
The actual sending of the results is to be done in a separate component
that would:
1) Call Next() to get the next report to send.
2) Call Confirm() to confirm that the report has been sent.
3) Call Upstream() if the report has been moderated and needs to be sent
to e.g. public mailing lists.
|
| |
|
|
| |
Run differential fuzzing as a workflow step.
|
| | |
|
| |
|
|
| |
Report the findings only for the boot test of the patched kernel.
|
|
|
Run a smoke test on the base kernel build and report back the results.
|
