Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Set of patches intended to make UBSAN work when fuzzing M2. Currently UBSAN is showing reports that do not appear to be security related during initialization. This allows the fuzzing session to halt on UBSAN reports and be cleaner. I have encountered 2 integer overflows issues in the native programs and think UBSAN would be beneficial for those running the Fuzzers.
The patches are for the Clang build. IIRC when testing, GCC's UBSAN had more false positives (that appeared during compilation) than Clang and was not supporting all sanitize flags of UBSAN (ie. less stable).
I also added unsigned-overflow checks to
with-ubsan.mk
, as this is targeted for fuzzing.Note:
fd_exec_instr_test.c
is an exception that requires modifying CFLAGS for -fno-sanitize=undefined (I did not manage to make it work with__attribute__((no_sanitize("undefined")))
nor__attribute__((no_sanitize("nullability")))
). This does not prevent dependencies such as native programs to be compiled in with UBSAN.