aboutsummaryrefslogtreecommitdiffstats
path: root/sys/linux/dev_random.txt.const
diff options
context:
space:
mode:
authorAleksandr Nogikh <nogikh@google.com>2024-04-30 14:57:05 +0200
committerAleksandr Nogikh <nogikh@google.com>2024-05-02 17:00:15 +0000
commitf61ed74922653fa99fbc3f915d36f6741e2df41c (patch)
tree8e54d89ab30294b1b03d42e886cf9ce61d5e5e14 /sys/linux/dev_random.txt.const
parent22ee48a2879809608f79cc23c914859fa2335d59 (diff)
syz-manager: abort fuzzing immediately after crash detection
If the crash did not result in a panic, we continue normal fuzzing operation for several more seconds until a delay has passed and the VM was stopped. It results in 20-30 more programs that are: 1) Run on a potentially corrupted machine. 2) Litter the logs -- these programs are definitely not related to the crash. 3) Make it trickier to automatically track crash risk for individual syscalls/programs (if we get to this). Add an option to vm.Run that allows to determine a crash immediatey after it was detected. Use it to stop program exchange and program injection in rpc.go.
Diffstat (limited to 'sys/linux/dev_random.txt.const')
0 files changed, 0 insertions, 0 deletions