aaa94a1b3c
The timeout mechanism won't work if SIGALRM is blocked. This changes unmasks SIGALRM when the timer is installed. This doesn't completely solve the problem, as the fuzzer could trigger some device activity that re-masks SIGALRM. However, there are currently no inputs on OSS-Fuzz that re-mask SIGALRM and timeout. If that turns out to be a real issue, we could try to hook sigmask-type calls, or use a separate timer thread. Based-on: <20210713150037.9297-1-alxndr@bu.edu> Signed-off-by: Alexander Bulekov <alxndr@bu.edu> Reviewed-by: Darren Kenny <darren.kenny@oracle.com> |
||
|---|---|---|
| .. | ||
| fork_fuzz.c | ||
| fork_fuzz.h | ||
| fork_fuzz.ld | ||
| fuzz.c | ||
| fuzz.h | ||
| generic_fuzz.c | ||
| generic_fuzz_configs.h | ||
| i440fx_fuzz.c | ||
| meson.build | ||
| qos_fuzz.c | ||
| qos_fuzz.h | ||
| qtest_wrappers.c | ||
| virtio_blk_fuzz.c | ||
| virtio_net_fuzz.c | ||
| virtio_scsi_fuzz.c | ||