summaryrefslogtreecommitdiff
path: root/scripts/check-function-names.sh
diff options
context:
space:
mode:
authorJosh Poimboeuf <jpoimboe@kernel.org>2025-11-20 23:14:17 +0300
committerPeter Zijlstra <peterz@infradead.org>2025-11-21 12:04:09 +0300
commit2c715c9de293b6c05bcdff1c22a7626f3bb42492 (patch)
tree78f39fb14b5ef6a06adafe28c0733a739caa9e12 /scripts/check-function-names.sh
parentda6202139aef11c3c5881176e6e3184d88d8a0d9 (diff)
downloadlinux-2c715c9de293b6c05bcdff1c22a7626f3bb42492.tar.xz
media: atomisp: gc2235: Fix namespace collision and startup() section placement with -ffunction-sections
When compiled with -ffunction-sections (e.g., for LTO, livepatch, dead code elimination, AutoFDO, or Propeller), the startup() function gets compiled into the .text.startup section (or in some cases .text.startup.constprop.0 or .text.startup.isra.0). However, the .text.startup and .text.startup.* sections are also used by the compiler for __attribute__((constructor)) code. This naming conflict causes the vmlinux linker script to wrongly place startup() function code in .init.text, which gets freed during boot. Some builds have a mix of objects, both with and without -ffunctions-sections, so it's not possible for the linker script to disambiguate with #ifdef CONFIG_FUNCTION_SECTIONS or similar. This means that "startup" unfortunately needs to be prohibited as a function name. Rename startup() to gc2235_startup(). Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Link: https://patch.msgid.link/d28103a6edf7beceb5e3c6fa24e49dbad1350389.1763669451.git.jpoimboe@kernel.org
Diffstat (limited to 'scripts/check-function-names.sh')
0 files changed, 0 insertions, 0 deletions