diff options
| author | Kees Cook <keescook@chromium.org> | 2023-04-07 22:27:13 +0300 |
|---|---|---|
| committer | Kees Cook <keescook@chromium.org> | 2024-03-01 00:38:02 +0300 |
| commit | 475ddf1fce1ec4826c8dda40ec59f7f83a7aadb8 (patch) | |
| tree | e9c16bb1b04f47c6fbeb51e532a6271dd1ebb05c /arch/x86/boot | |
| parent | 99db710f768e988e70f1164537bf533a017be24d (diff) | |
| download | linux-475ddf1fce1ec4826c8dda40ec59f7f83a7aadb8.tar.xz | |
fortify: Split reporting and avoid passing string pointer
In preparation for KUnit testing and further improvements in fortify
failure reporting, split out the report and encode the function and access
failure (read or write overflow) into a single u8 argument. This mainly
ends up saving a tiny bit of space in the data segment. For a defconfig
with FORTIFY_SOURCE enabled:
$ size gcc/vmlinux.before gcc/vmlinux.after
text data bss dec hex filename
26132309 9760658 2195460 38088427 2452eeb gcc/vmlinux.before
26132386 9748382 2195460 38076228 244ff44 gcc/vmlinux.after
Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'arch/x86/boot')
| -rw-r--r-- | arch/x86/boot/compressed/misc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/boot/compressed/misc.c b/arch/x86/boot/compressed/misc.c index b99e08e6815b..c9971b9dbb09 100644 --- a/arch/x86/boot/compressed/misc.c +++ b/arch/x86/boot/compressed/misc.c @@ -496,7 +496,7 @@ asmlinkage __visible void *extract_kernel(void *rmode, unsigned char *output) return output + entry_offset; } -void fortify_panic(const char *name) +void __fortify_panic(const u8 reason) { error("detected buffer overflow"); } |