be58f71037
While the run-time testing of FORTIFY_SOURCE is already present in LKDTM, there is no testing of the expected compile-time detections. In preparation for correctly supporting FORTIFY_SOURCE under Clang, adding additional FORTIFY_SOURCE defenses, and making sure FORTIFY_SOURCE doesn't silently regress with GCC, introduce a build-time test suite that checks each expected compile-time failure condition. As this is relatively backwards from standard build rules in the sense that a successful test is actually a compile _failure_, create a wrapper script to check for the correct errors, and wire it up as a dummy dependency to lib/string.o, collecting the results into a log file artifact. Signed-off-by: Kees Cook <keescook@chromium.org> |
||
---|---|---|
.. | ||
read_overflow2-memcmp.c | ||
read_overflow2-memcpy.c | ||
read_overflow2-memmove.c | ||
read_overflow-memchr_inv.c | ||
read_overflow-memchr.c | ||
read_overflow-memcmp.c | ||
read_overflow-memscan.c | ||
test_fortify.h | ||
write_overflow-memcpy.c | ||
write_overflow-memmove.c | ||
write_overflow-memset.c | ||
write_overflow-strcpy-lit.c | ||
write_overflow-strcpy.c | ||
write_overflow-strlcpy-src.c | ||
write_overflow-strlcpy.c | ||
write_overflow-strncpy-src.c | ||
write_overflow-strncpy.c | ||
write_overflow-strscpy.c |