aboutsummaryrefslogtreecommitdiffstats
path: root/lib/debugobjects.c
diff options
context:
space:
mode:
authorKees Cook <[email protected]>2023-05-31 00:34:15 +0000
committerKees Cook <[email protected]>2023-06-01 18:24:51 +0000
commit4ce1e94175696b8f5f6fa29f09f7ef56724ddc2a (patch)
tree950a7a28ba09ec59aac330dd80477686273515c5 /lib/debugobjects.c
parentx86/purgatory: Do not use fortified string functions (diff)
downloadkernel-4ce1e94175696b8f5f6fa29f09f7ef56724ddc2a.tar.gz
kernel-4ce1e94175696b8f5f6fa29f09f7ef56724ddc2a.zip
s390/purgatory: Do not use fortified string functions
With the addition of -fstrict-flex-arrays=3, struct sha256_state's trailing array is no longer ignored by CONFIG_FORTIFY_SOURCE: struct sha256_state { u32 state[SHA256_DIGEST_SIZE / 4]; u64 count; u8 buf[SHA256_BLOCK_SIZE]; }; This means that the memcpy() calls with "buf" as a destination in sha256.c's code will attempt to perform run-time bounds checking, which could lead to calling missing functions, specifically a potential WARN_ONCE, which isn't callable from purgatory. Reported-by: Thorsten Leemhuis <[email protected]> Closes: https://lore.kernel.org/lkml/[email protected]/ Bisected-by: "Joan Bruguera Micó" <[email protected]> Fixes: df8fc4e934c1 ("kbuild: Enable -fstrict-flex-arrays=3") Cc: Heiko Carstens <[email protected]> Cc: Vasily Gorbik <[email protected]> Cc: Alexander Gordeev <[email protected]> Cc: Christian Borntraeger <[email protected]> Cc: Sven Schnelle <[email protected]> Cc: Masahiro Yamada <[email protected]> Cc: Linux Kernel Functional Testing <[email protected]> Cc: Nathan Chancellor <[email protected]> Cc: "Gustavo A. R. Silva" <[email protected]> Cc: [email protected] Signed-off-by: Kees Cook <[email protected]> Reviewed-by: Nathan Chancellor <[email protected]> Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/debugobjects.c')
0 files changed, 0 insertions, 0 deletions