Centos-kernel-stream-9/lib/test_fortify/write_overflow-memset.c

// SPDX-License-Identifier: GPL-2.0-only
#define TEST	\
	memset(instance.buf, 0x5A, sizeof(large_src))

#include "test_fortify.h"
fortify: Add compile-time FORTIFY_SOURCE tests Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2139493 Conflicts: Context conflict because bb95ebbe89a7 has been already backported commit be58f7103700a68d5c7ca60a2bc0b309907599ab Author: Kees Cook <keescook@chromium.org> Date: Tue Apr 20 23:22:52 2021 -0700 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> Signed-off-by: Josef Oskera <joskera@redhat.com> 2022-12-10 21:59:40 +00:00			`// SPDX-License-Identifier: GPL-2.0-only`
			`#define TEST \`
			`memset(instance.buf, 0x5A, sizeof(large_src))`

			`#include "test_fortify.h"`