objtool, xen: Fix INSN_SYSCALL / INSN_SYSRET semantics
authorJosh Poimboeuf <jpoimboe@kernel.org>
Tue, 8 Apr 2025 07:02:16 +0000 (00:02 -0700)
committerIngo Molnar <mingo@kernel.org>
Tue, 8 Apr 2025 07:14:12 +0000 (09:14 +0200)
commit2dbbca9be4e5ed68d0972a2bcf4561d9cb85b7b7
treedfbe503ba0737da4dcdd8bc0c6cf261ce4669e32
parent9f9cc012c2cbac4833746a0182e06a8eec940d19
objtool, xen: Fix INSN_SYSCALL / INSN_SYSRET semantics

Objtool uses an arbitrary rule for INSN_SYSCALL and INSN_SYSRET that
almost works by accident: if it's in a function, control flow continues
after the instruction, otherwise it terminates.

That behavior should instead be based on the semantics of the underlying
instruction.  Change INSN_SYSCALL to always preserve control flow and
INSN_SYSRET to always terminate it.

The changed semantic for INSN_SYSCALL requires a tweak to the
!CONFIG_IA32_EMULATION version of xen_entry_SYSCALL_compat().  In Xen,
SYSCALL is a hypercall which usually returns.  But in this case it's a
hypercall to IRET which doesn't return.  Add UD2 to tell objtool to
terminate control flow, and to prevent undefined behavior at runtime.

Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Juergen Gross <jgross@suse.com> # for the Xen part
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Link: https://lore.kernel.org/r/19453dfe9a0431b7f016e9dc16d031cad3812a50.1744095216.git.jpoimboe@kernel.org
arch/x86/xen/xen-asm.S
tools/objtool/check.c