summaryrefslogtreecommitdiff
path: root/scripts/kconfig/tests/conditional_dep/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorJosh Poimboeuf <jpoimboe@kernel.org>2026-04-23 15:53:17 -0700
committerJosh Poimboeuf <jpoimboe@kernel.org>2026-05-04 21:16:07 -0700
commitfc0bb9915bce0c333f918ca76958d804ccd79f89 (patch)
tree4623f5e23f16b8d185f7a59b1f61c625947594c7 /scripts/kconfig/tests/conditional_dep/git@git.tavy.me:linux.git
parentcca84cb12908f1cfcecaef80a7692017e2d6a945 (diff)
objtool: Grow __cfi_* prefix symbols for all CFI+CALL_PADDING
For all CONFIG_CFI+CONFIG_CALL_PADDING configs, for C functions, the __cfi_ symbols only cover the 5-byte kCFI type hash. After that there also N bytes of NOP padding between the hash and the function entry which aren't associated with any symbol. The NOPs can be replaced with actual code at runtime. Without a symbol, unwinders and tooling have no way of knowing where those bytes belong. Grow the existing __cfi_* symbols to fill that gap. Note that assembly functions with SYM_TYPED_FUNC_START() aren't affected by this issue, their __cfi_ symbols also cover the padding. Also, CONFIG_PREFIX_SYMBOLS has no reason to exist: CONFIG_CALL_PADDING is what causes the compiler to emit NOP padding before function entry (via -fpatchable-function-entry), so it's the right condition for creating prefix symbols. Remove CONFIG_PREFIX_SYMBOLS, as it's no longer needed. Simplify the LONGEST_SYM_KUNIT_TEST dependency accordingly. Rework objtool's arguments a bit to handle the variety of prefix/cfi-related cases. Suggested-by: Peter Zijlstra <peterz@infradead.org> Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
Diffstat (limited to 'scripts/kconfig/tests/conditional_dep/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions