From: Andrew Cooper <Andrew.Cooper3@citrix.com>
To: Peter Zijlstra <peterz@infradead.org>,
"x86@kernel.org" <x86@kernel.org>,
"joao@overdrivepizza.com" <joao@overdrivepizza.com>,
"hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"jpoimboe@redhat.com" <jpoimboe@redhat.com>,
"Juergen Gross" <jgross@suse.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ndesaulniers@google.com" <ndesaulniers@google.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"samitolvanen@google.com" <samitolvanen@google.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"alyssa.milburn@intel.com" <alyssa.milburn@intel.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>
Subject: Re: [PATCH 19/29] x86/ibt,xen: Annotate away warnings
Date: Fri, 18 Feb 2022 20:24:41 +0000 [thread overview]
Message-ID: <e5b93f0a-a28c-8c63-0193-4b4d0db509ab@citrix.com> (raw)
In-Reply-To: <20220218171409.696743603@infradead.org>
On 18/02/2022 16:49, Peter Zijlstra wrote:
> The xen_iret ENDBR is needed for pre-alternative code calling the
> pv_ops using indirect calls.
>
> The rest look like hypervisor entry points which will be IRET like
> transfers and as such don't need ENDBR.
That's up for debate. Mechanically, yes - they're IRET or SYSERET.
Logically however, they're entrypoints registered with Xen, so following
the spec, Xen ought to force WAIT-FOR-ENDBR.
Or we could argue that said entrypoints are registered in Xen.
The case for ENDBR for the IDT vectors is quite obviously - a stray
write into the IDT can modify the entrypoint, and ENDBR limits an
attacker's choices.
OTOH, the SYSCALL and SYSENTER entrypoints are latched in MSRs, and if
you've got a sufficiently large security hole that the attacker can
write these MSRs, you have already lost. I'm not aware of any extra
security you get from forcing WAIT-FOR-ENDBR in the SYSCALL/SYSENTER
flow, and suspect it was like that just for consistency.
Under Xen PV, all entrypoints are configured by explicit hypercall, not
via a shared memory structure, so better match the MSR model for
native. I could probably be argued away from having a RMW of MSR_U_CET
in the event delivery fastpath.
I'd be tempted to leave the ENDBR's in. It feels like a safer default
until we figure out how to paravirt IBT properly.
> The hypercall page comes from the hypervisor, there might or might not
> be ENDBR there, not our problem.
Xen will make sure that the hypercall page contains ENDBR's if CET-IBT
is available for the guest to use. Perhaps...
> --- a/arch/x86/xen/xen-head.S
> +++ b/arch/x86/xen/xen-head.S
> @@ -25,8 +25,8 @@
> SYM_CODE_START(hypercall_page)
> .rept (PAGE_SIZE / 32)
> UNWIND_HINT_FUNC
> - .skip 31, 0x90
> - RET
> + ANNOTATE_NOENDBR
> + .skip 32, 0xcc
// Xen writes the hypercall page, and will sort out ENDBR
?
Also, somewhere in this series needs:
diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c
index 5004feb16783..e30f77264ee6 100644
--- a/arch/x86/xen/enlighten_pv.c
+++ b/arch/x86/xen/enlighten_pv.c
@@ -624,6 +624,7 @@ static struct trap_array_entry trap_array[] = {
TRAP_ENTRY(exc_coprocessor_error, false ),
TRAP_ENTRY(exc_alignment_check, false ),
TRAP_ENTRY(exc_simd_coprocessor_error, false ),
+ TRAP_ENTRY(exc_control_protection, false ),
};
static bool __ref get_trap_addr(void **addr, unsigned int ist)
diff --git a/arch/x86/xen/xen-asm.S b/arch/x86/xen/xen-asm.S
index 444d824775f6..6f077aedd561 100644
--- a/arch/x86/xen/xen-asm.S
+++ b/arch/x86/xen/xen-asm.S
@@ -147,6 +147,7 @@ xen_pv_trap asm_exc_page_fault
xen_pv_trap asm_exc_spurious_interrupt_bug
xen_pv_trap asm_exc_coprocessor_error
xen_pv_trap asm_exc_alignment_check
+xen_pv_trap asm_exc_control_protection
#ifdef CONFIG_X86_MCE
xen_pv_trap asm_xenpv_exc_machine_check
#endif /* CONFIG_X86_MCE */
at a minimum, and possibly also:
diff --git a/arch/x86/xen/xen-asm.S b/arch/x86/xen/xen-asm.S
index 444d824775f6..96db5c50a6e7 100644
--- a/arch/x86/xen/xen-asm.S
+++ b/arch/x86/xen/xen-asm.S
@@ -124,7 +124,7 @@ SYM_CODE_START(xen_\name)
UNWIND_HINT_EMPTY
pop %rcx
pop %r11
- jmp \name
+ jmp \name + 4 * IS_ENABLED(CONFIG_X86_IBT)
SYM_CODE_END(xen_\name)
_ASM_NOKPROBE(xen_\name)
.endm
(Entirely untested.)
~Andrew
next prev parent reply other threads:[~2022-02-18 20:24 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 16:49 [PATCH 00/29] x86: Kernel IBT Peter Zijlstra
2022-02-18 16:49 ` [PATCH 01/29] static_call: Avoid building empty .static_call_sites Peter Zijlstra
2022-02-18 16:49 ` [PATCH 02/29] x86/module: Fix the paravirt vs alternative order Peter Zijlstra
2022-02-18 20:28 ` Josh Poimboeuf
2022-02-18 21:22 ` Peter Zijlstra
2022-02-18 23:28 ` Josh Poimboeuf
2022-02-18 16:49 ` [PATCH 03/29] objtool: Add --dry-run Peter Zijlstra
2022-02-18 16:49 ` [PATCH 04/29] x86/livepatch: Validate __fentry__ location Peter Zijlstra
2022-02-18 21:08 ` Josh Poimboeuf
2022-02-23 10:09 ` Peter Zijlstra
2022-02-23 10:21 ` Miroslav Benes
2022-02-23 10:57 ` Peter Zijlstra
2022-02-23 12:41 ` Steven Rostedt
2022-02-23 14:05 ` Peter Zijlstra
2022-02-23 14:16 ` Steven Rostedt
2022-02-23 14:23 ` Steven Rostedt
2022-02-23 14:33 ` Steven Rostedt
2022-02-23 14:49 ` Peter Zijlstra
2022-02-23 15:54 ` Peter Zijlstra
2022-02-18 16:49 ` [PATCH 05/29] x86: Base IBT bits Peter Zijlstra
2022-02-18 20:49 ` Andrew Cooper
2022-02-18 21:11 ` David Laight
2022-02-18 21:24 ` Andrew Cooper
2022-02-18 22:37 ` David Laight
2022-02-18 21:26 ` Peter Zijlstra
2022-02-18 21:14 ` Josh Poimboeuf
2022-02-18 21:21 ` Peter Zijlstra
2022-02-18 22:12 ` Joao Moreira
2022-02-19 1:07 ` Edgecombe, Rick P
2022-02-18 16:49 ` [PATCH 06/29] x86/ibt: Add ANNOTATE_NOENDBR Peter Zijlstra
2022-02-18 16:49 ` [PATCH 07/29] x86/entry: Sprinkle ENDBR dust Peter Zijlstra
2022-02-19 0:23 ` Josh Poimboeuf
2022-02-19 23:08 ` Peter Zijlstra
2022-02-19 0:36 ` Josh Poimboeuf
2022-02-18 16:49 ` [PATCH 08/29] x86/linkage: Add ENDBR to SYM_FUNC_START*() Peter Zijlstra
2022-02-18 16:49 ` [PATCH 09/29] x86/ibt,paravirt: Sprinkle ENDBR Peter Zijlstra
2022-02-18 16:49 ` [PATCH 10/29] x86/bpf: Add ENDBR instructions to prologue Peter Zijlstra
2022-02-18 16:49 ` [PATCH 11/29] x86/ibt,crypto: Add ENDBR for the jump-table entries Peter Zijlstra
2022-02-18 16:49 ` [PATCH 12/29] x86/ibt,kvm: Add ENDBR to fastops Peter Zijlstra
2022-02-18 16:49 ` [PATCH 13/29] x86/ibt,ftrace: Add ENDBR to samples/ftrace Peter Zijlstra
2022-02-18 16:49 ` [PATCH 14/29] x86/ibt: Add IBT feature, MSR and #CP handling Peter Zijlstra
2022-02-18 19:31 ` Andrew Cooper
2022-02-18 21:15 ` Peter Zijlstra
2022-02-19 1:20 ` Edgecombe, Rick P
2022-02-19 1:21 ` Josh Poimboeuf
2022-02-19 9:24 ` Peter Zijlstra
2022-02-21 8:24 ` Kees Cook
2022-02-22 4:38 ` Edgecombe, Rick P
2022-02-22 9:32 ` Peter Zijlstra
2022-02-18 16:49 ` [PATCH 15/29] x86: Disable IBT around firmware Peter Zijlstra
2022-02-21 8:27 ` Kees Cook
2022-02-21 10:06 ` Peter Zijlstra
2022-02-21 13:22 ` Peter Zijlstra
2022-02-21 15:54 ` Kees Cook
2022-02-21 16:10 ` Peter Zijlstra
2022-02-18 16:49 ` [PATCH 16/29] x86/bugs: Disable Retpoline when IBT Peter Zijlstra
2022-02-19 2:15 ` Josh Poimboeuf
2022-02-22 15:00 ` Peter Zijlstra
2022-02-25 0:19 ` Josh Poimboeuf
2022-02-18 16:49 ` [PATCH 17/29] x86/ibt: Annotate text references Peter Zijlstra
2022-02-19 5:22 ` Josh Poimboeuf
2022-02-19 9:39 ` Peter Zijlstra
2022-02-18 16:49 ` [PATCH 18/29] x86/ibt,ftrace: Annotate ftrace code patching Peter Zijlstra
2022-02-18 16:49 ` [PATCH 19/29] x86/ibt,xen: Annotate away warnings Peter Zijlstra
2022-02-18 20:24 ` Andrew Cooper [this message]
2022-02-18 21:05 ` Peter Zijlstra
2022-02-18 23:07 ` Andrew Cooper
2022-02-21 14:20 ` Peter Zijlstra
2022-02-18 16:49 ` [PATCH 20/29] x86/ibt,sev: Annotations Peter Zijlstra
2022-02-18 16:49 ` [PATCH 21/29] objtool: Rename --duplicate to --lto Peter Zijlstra
2022-02-26 19:42 ` Josh Poimboeuf
2022-02-26 21:48 ` Josh Poimboeuf
2022-02-28 11:05 ` Peter Zijlstra
2022-02-28 18:32 ` Josh Poimboeuf
2022-02-28 20:09 ` Peter Zijlstra
2022-02-28 20:18 ` Josh Poimboeuf
2022-03-01 14:19 ` Miroslav Benes
2022-02-18 16:49 ` [PATCH 22/29] Kbuild: Prepare !CLANG whole module objtool Peter Zijlstra
2022-02-18 16:49 ` [PATCH 23/29] objtool: Read the NOENDBR annotation Peter Zijlstra
2022-02-18 16:49 ` [PATCH 24/29] x86/text-patching: Make text_gen_insn() IBT aware Peter Zijlstra
2022-02-24 1:18 ` Joao Moreira
2022-02-24 9:10 ` Peter Zijlstra
2022-02-18 16:49 ` [PATCH 25/29] x86/ibt: Dont generate ENDBR in .discard.text Peter Zijlstra
2022-02-18 16:49 ` [PATCH 26/29] objtool: Add IBT validation / fixups Peter Zijlstra
2022-02-18 16:49 ` [PATCH 27/29] x86/ibt: Finish --ibt-fix-direct on module loading Peter Zijlstra
2022-02-18 16:49 ` [PATCH 28/29] x86/ibt: Ensure module init/exit points have references Peter Zijlstra
2022-02-18 16:49 ` [PATCH 29/29] x86/alternative: Use .ibt_endbr_sites to seal indirect calls Peter Zijlstra
2022-02-19 1:29 ` [PATCH 00/29] x86: Kernel IBT Edgecombe, Rick P
2022-02-19 9:58 ` Peter Zijlstra
2022-02-19 16:00 ` Andrew Cooper
2022-02-21 8:42 ` Kees Cook
2022-02-21 9:24 ` Peter Zijlstra
2022-02-23 7:26 ` Kees Cook
2022-02-24 16:47 ` Mike Rapoport
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5b93f0a-a28c-8c63-0193-4b4d0db509ab@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=alyssa.milburn@intel.com \
--cc=hjl.tools@gmail.com \
--cc=jgross@suse.com \
--cc=joao@overdrivepizza.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®