| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | all: reformat C/C++ files | Dmitry Vyukov | 2026-01-19 | 1 | -29/+29 |
| | | |||||
| * | pkg/kfuzztest: skip tests when cannot build Linux | Aleksandr Nogikh | 2025-10-06 | 1 | -0/+4 |
| | | | | | Otherwise we get the "cant-build-linux-on-openbsd" error. | ||||
| * | pkg/kfuzztest: skip description generation test on non-amd64 arches | Alexander Egorenkov | 2025-09-30 | 1 | -0/+3 |
| | | | | | | | | Skip the description generation test on non-x86 architectures if no cross-compiler could be found. Signed-off-by: Alexander Egorenkov <eaibmz@gmail.com> | ||||
| * | prog: fix syz_kfuzztest_run allocation strategy | Ethan Graham | 2025-09-22 | 3 | -3/+4 |
| | | | | | | | | | | | | | | | | | | | | | Previously, the generated KFuzzTest programs were reusing the address of the top-level input struct. A problem could arise when the encoded blob is large and overflows into another allocated region - this certainly happens in the case where the input struct points to some large char buffer, for example. While this wasn't directly a problem, it could lead to racy behavior when running KFuzzTest targets concurrently. To fix this, we now introduce an additional buffer parameter into syz_kfuzztest_run that is as big as the maximum accepted input size in the KFuzzTest kernel code. When this buffer is allocated, we ensure that we have some allocated space in the program that can hold the entire encoded input. This works in practice, but has not been tested with concurrent KFuzzTest executions yet. | ||||
| * | pkg/kfuzztest: add pkg/kfuzztest | Ethan Graham | 2025-09-22 | 12 | -0/+1340 |
| Add a new package, pkg/kfuzztest, that implements dynamic discovery of KFuzzTest targets by parsing a vmlinux kernel binary. Signed-off-by: Ethan Graham <ethangraham@google.com> | |||||
 |
index : syz | |
| Unnamed repository; edit this file 'description' to name the repository. | root |
| aboutsummaryrefslogtreecommitdiffstats |