aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/check-function-names.sh
diff options
context:
space:
mode:
authorJosh Poimboeuf <jpoimboe@kernel.org>2025-11-20 12:14:19 -0800
committerPeter Zijlstra <peterz@infradead.org>2025-11-21 10:04:10 +0100
commit31863337138a0482d614f1090727dac87c936959 (patch)
tree2a3cd1c3ab82d72737a274fe8572ac58bdf09afc /scripts/check-function-names.sh
parent845c09e4744f111eae894ad3b67a369bb43d50fb (diff)
downloadlinux-31863337138a0482d614f1090727dac87c936959.tar.gz
tty: synclink_gt: 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 startup_hw(). For consistency, also rename its shutdown() counterpart to shutdown_hw(). 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/f0ee750f35c878172cc09916a0724b74e62eadc2.1763669451.git.jpoimboe@kernel.org
Diffstat (limited to 'scripts/check-function-names.sh')
0 files changed, 0 insertions, 0 deletions