summaryrefslogtreecommitdiffstats
path: root/fs/ntfs/usnjrnl.c
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2021-04-21 08:22:52 +0200
committerKees Cook <keescook@chromium.org>2021-10-18 21:28:52 +0200
commitbe58f7103700a68d5c7ca60a2bc0b309907599ab (patch)
treed9caaca50a2c98c6458372fac636bee254b1da9e /fs/ntfs/usnjrnl.c
parentfortify: Allow strlen() and strnlen() to pass compile-time known lengths (diff)
downloadlinux-be58f7103700a68d5c7ca60a2bc0b309907599ab.tar.xz
linux-be58f7103700a68d5c7ca60a2bc0b309907599ab.zip
fortify: Add compile-time FORTIFY_SOURCE tests
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>
Diffstat (limited to 'fs/ntfs/usnjrnl.c')
0 files changed, 0 insertions, 0 deletions