From: Daniel Palmer Date: Sat, 25 Apr 2026 11:13:15 +0000 (+0900) Subject: tools/nolibc: Don't use stack protector before setting it up X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=5b1528c33befa323c783bbaf9a8a67371e3bcbd5;p=thirdparty%2Fkernel%2Flinux.git tools/nolibc: Don't use stack protector before setting it up The stack protector is configured in _start_c() so we shouldn't use it before then. Add __nolibc_no_stack_protector to _start_c() to avoid the compiler generating stack protector code for _start_c() and thus using it before its configured. Signed-off-by: Daniel Palmer Link: https://patch.msgid.link/20260425111315.3191461-3-daniel@thingy.jp Signed-off-by: Thomas Weißschuh --- diff --git a/tools/include/nolibc/crt.h b/tools/include/nolibc/crt.h index f38590a05adf0..78124b6598a72 100644 --- a/tools/include/nolibc/crt.h +++ b/tools/include/nolibc/crt.h @@ -47,7 +47,7 @@ char *__nolibc_program_invocation_short_name(char *long_name) #endif /* NOLIBC_IGNORE_ERRNO */ void _start_c(long *sp); -__attribute__((weak,used)) __nolibc_no_sanitize_undefined +__attribute__((weak,used)) __nolibc_no_sanitize_undefined __nolibc_no_stack_protector void _start_c(long *sp) { long argc;