Bug: Ctrl-C causes the fuzzer to store a "bug" violation

microsoft / sca-fuzzer

Revizor - a fuzzer to search for microarchitectural leaks in CPUs

https://microsoft.github.io/sca-fuzzer/

MIT License

114 stars 35 forks source link

Bug: Ctrl-C causes the fuzzer to store a "bug" violation #108

Open OleksiiOleksenko opened 3 months ago

OleksiiOleksenko commented 3 months ago

Copied from @brianfu's PR:

Using "CTRL+C" to cancel the run halfway will now cause it to spit out a "bug" violation for the canceled run (assuming this is to detect archfuzz bugs). Be careful to distinguish between actual architectural bugs and the false positives that are just testing artifacts.

OleksiiOleksenko commented 3 months ago

@brianfu What was the command/config file necessary to reproduce this bug? (I can't reproduce with normal fuzzing)

brianfu commented 3 months ago

I used this (with the bash variables set):

python $RVZR_DIR/revizor.py tfuzz -s $RVZR_DIR/base.json -n $TEST_PROGS -i $TEST_INPUTS -c $CFG_DIR/template_nonif.yaml -w $VIOL_DIR -t $CFG_DIR/template_VA.asm --nonstop &> $SCRIPT_DIR/output.out

I suspect this might be an artifact of things not perfectly being killed as a result of using --nonstop (The executor is killed but the python script keeps going); If so, it may not necessarily be a bug (or at least not one worth fixing).