From: Deepak Gupta <debug@rivosinc.com>
To: "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Conor Dooley" <conor@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Christian Brauner" <brauner@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Oleg Nesterov" <oleg@redhat.com>,
"Eric Biederman" <ebiederm@xmission.com>,
"Kees Cook" <kees@kernel.org>, "Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <shuah@kernel.org>, "Jann Horn" <jannh@google.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-riscv@lists.infradead.org,
devicetree@vger.kernel.org, linux-arch@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
alistair.francis@wdc.com, richard.henderson@linaro.org,
jim.shu@sifive.com, andybnac@gmail.com, kito.cheng@sifive.com,
charlie@rivosinc.com, atishp@rivosinc.com, evan@rivosinc.com,
cleger@rivosinc.com, alexghiti@rivosinc.com,
samitolvanen@google.com, broonie@kernel.org,
rick.p.edgecombe@intel.com, rust-for-linux@vger.kernel.org,
Zong Li <zong.li@sifive.com>
Subject: Re: [PATCH v13 05/28] riscv: usercfi state for task and save/restore of CSR_SSP on trap entry/exit
Date: Thu, 24 Apr 2025 00:25:34 -0700 [thread overview]
Message-ID: <aAnnbtABLTL81uEY@debug.ba.rivosinc.com> (raw)
In-Reply-To: <20250424-v5_user_cfi_series-v13-5-971437de586a@rivosinc.com>
On Thu, Apr 24, 2025 at 12:20:20AM -0700, Deepak Gupta wrote:
>Carves out space in arch specific thread struct for cfi status and shadow
>stack in usermode on riscv.
>
>This patch does following
>- defines a new structure cfi_status with status bit for cfi feature
>- defines shadow stack pointer, base and size in cfi_status structure
>- defines offsets to new member fields in thread in asm-offsets.c
>- Saves and restore shadow stack pointer on trap entry (U --> S) and exit
> (S --> U)
>
>Shadow stack save/restore is gated on feature availiblity and implemented
>using alternative. CSR can be context switched in `switch_to` as well but
>soon as kernel shadow stack support gets rolled in, shadow stack pointer
>will need to be switched at trap entry/exit point (much like `sp`). It can
>be argued that kernel using shadow stack deployment scenario may not be as
>prevalant as user mode using this feature. But even if there is some
>minimal deployment of kernel shadow stack, that means that it needs to be
>supported. And thus save/restore of shadow stack pointer in entry.S instead
>of in `switch_to.h`.
>
>Reviewed-by: Charlie Jenkins <charlie@rivosinc.com>
>Reviewed-by: Zong Li <zong.li@sifive.com>
>Reviewed-by: Alexandre Ghiti <alexghiti@rivosinc.com>
>Signed-off-by: Deepak Gupta <debug@rivosinc.com>
>---
> arch/riscv/include/asm/processor.h | 1 +
> arch/riscv/include/asm/thread_info.h | 3 +++
> arch/riscv/include/asm/usercfi.h | 24 ++++++++++++++++++++++++
> arch/riscv/kernel/asm-offsets.c | 4 ++++
> arch/riscv/kernel/entry.S | 23 +++++++++++++++++++++++
> 5 files changed, 55 insertions(+)
>
>diff --git a/arch/riscv/include/asm/processor.h b/arch/riscv/include/asm/processor.h
>index e3aba3336e63..d851bb5c6da0 100644
>--- a/arch/riscv/include/asm/processor.h
>+++ b/arch/riscv/include/asm/processor.h
>@@ -14,6 +14,7 @@
>
> #include <asm/ptrace.h>
> #include <asm/hwcap.h>
>+#include <asm/usercfi.h>
>
> #define arch_get_mmap_end(addr, len, flags) \
> ({ \
>diff --git a/arch/riscv/include/asm/thread_info.h b/arch/riscv/include/asm/thread_info.h
>index f5916a70879a..a0cfe00c2ca6 100644
>--- a/arch/riscv/include/asm/thread_info.h
>+++ b/arch/riscv/include/asm/thread_info.h
>@@ -62,6 +62,9 @@ struct thread_info {
> long user_sp; /* User stack pointer */
> int cpu;
> unsigned long syscall_work; /* SYSCALL_WORK_ flags */
>+#ifdef CONFIG_RISCV_USER_CFI
>+ struct cfi_status user_cfi_state;
>+#endif
> #ifdef CONFIG_SHADOW_CALL_STACK
> void *scs_base;
> void *scs_sp;
>diff --git a/arch/riscv/include/asm/usercfi.h b/arch/riscv/include/asm/usercfi.h
>new file mode 100644
>index 000000000000..5f2027c51917
>--- /dev/null
>+++ b/arch/riscv/include/asm/usercfi.h
>@@ -0,0 +1,24 @@
>+/* SPDX-License-Identifier: GPL-2.0
>+ * Copyright (C) 2024 Rivos, Inc.
>+ * Deepak Gupta <debug@rivosinc.com>
>+ */
>+#ifndef _ASM_RISCV_USERCFI_H
>+#define _ASM_RISCV_USERCFI_H
>+
>+#ifndef __ASSEMBLY__
>+#include <linux/types.h>
>+
>+#ifdef CONFIG_RISCV_USER_CFI
>+struct cfi_status {
>+ unsigned long ubcfi_en : 1; /* Enable for backward cfi. */
>+ unsigned long rsvd : ((sizeof(unsigned long) * 8) - 1);
>+ unsigned long user_shdw_stk; /* Current user shadow stack pointer */
>+ unsigned long shdw_stk_base; /* Base address of shadow stack */
>+ unsigned long shdw_stk_size; /* size of shadow stack */
>+};
I didn't change this part yet. There are two comments from Radim here
1) Separate state of enabling/lock status from shadow stack pointer.
Same goes for landing pad in later patches. I am arguing that since
thread_info is already occupies two cachelines and there isn't any
effort to manage it within single cacheline, I am not sure if it's worth
the effort. Most likely comment is stale or doesn't have backed up data
behind it. Furthermore whenever state of enabling is accessed, most likely
shadow stack pointer, base pointer or size of shaodw stack will likely to
be accessed as well. Thus having all that in colocated cacheline would
actually be useful.
2) Convert enabling/lock status from bitfield to bool or accessed via bitmasks.
I am agreeing to feedback here and will do that once we converge on point 1.
>+
>+#endif /* CONFIG_RISCV_USER_CFI */
>+
>+#endif /* __ASSEMBLY__ */
>+
>+#endif /* _ASM_RISCV_USERCFI_H */
>diff --git a/arch/riscv/kernel/asm-offsets.c b/arch/riscv/kernel/asm-offsets.c
>index e89455a6a0e5..0c188aaf3925 100644
>--- a/arch/riscv/kernel/asm-offsets.c
>+++ b/arch/riscv/kernel/asm-offsets.c
>@@ -50,6 +50,10 @@ void asm_offsets(void)
> #endif
>
> OFFSET(TASK_TI_CPU_NUM, task_struct, thread_info.cpu);
>+#ifdef CONFIG_RISCV_USER_CFI
>+ OFFSET(TASK_TI_CFI_STATUS, task_struct, thread_info.user_cfi_state);
>+ OFFSET(TASK_TI_USER_SSP, task_struct, thread_info.user_cfi_state.user_shdw_stk);
>+#endif
> OFFSET(TASK_THREAD_F0, task_struct, thread.fstate.f[0]);
> OFFSET(TASK_THREAD_F1, task_struct, thread.fstate.f[1]);
> OFFSET(TASK_THREAD_F2, task_struct, thread.fstate.f[2]);
>diff --git a/arch/riscv/kernel/entry.S b/arch/riscv/kernel/entry.S
>index 33a5a9f2a0d4..f5531d82f7e7 100644
>--- a/arch/riscv/kernel/entry.S
>+++ b/arch/riscv/kernel/entry.S
>@@ -147,6 +147,20 @@ SYM_CODE_START(handle_exception)
>
> REG_L s0, TASK_TI_USER_SP(tp)
> csrrc s1, CSR_STATUS, t0
>+ /*
>+ * If previous mode was U, capture shadow stack pointer and save it away
>+ * Zero CSR_SSP at the same time for sanitization.
>+ */
>+ ALTERNATIVE("nops(4)",
>+ __stringify( \
>+ andi s2, s1, SR_SPP; \
>+ bnez s2, skip_ssp_save; \
>+ csrrw s2, CSR_SSP, x0; \
>+ REG_S s2, TASK_TI_USER_SSP(tp); \
>+ skip_ssp_save:),
>+ 0,
>+ RISCV_ISA_EXT_ZICFISS,
>+ CONFIG_RISCV_USER_CFI)
> csrr s2, CSR_EPC
> csrr s3, CSR_TVAL
> csrr s4, CSR_CAUSE
>@@ -236,6 +250,15 @@ SYM_CODE_START_NOALIGN(ret_from_exception)
> * structures again.
> */
> csrw CSR_SCRATCH, tp
>+
>+ ALTERNATIVE("nops(2)",
>+ __stringify( \
>+ REG_L s3, TASK_TI_USER_SSP(tp); \
>+ csrw CSR_SSP, s3),
>+ 0,
>+ RISCV_ISA_EXT_ZICFISS,
>+ CONFIG_RISCV_USER_CFI)
>+
> 1:
> #ifdef CONFIG_RISCV_ISA_V_PREEMPTIVE
> move a0, sp
>
>--
>2.43.0
>
next prev parent reply other threads:[~2025-04-24 7:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 7:20 [PATCH v13 00/28] riscv control-flow integrity for usermode Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 01/28] mm: VM_SHADOW_STACK definition for riscv Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 02/28] dt-bindings: riscv: zicfilp and zicfiss in dt-bindings (extensions.yaml) Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 03/28] riscv: zicfiss / zicfilp enumeration Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 04/28] riscv: zicfiss / zicfilp extension csr and bit definitions Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 05/28] riscv: usercfi state for task and save/restore of CSR_SSP on trap entry/exit Deepak Gupta
2025-04-24 7:25 ` Deepak Gupta [this message]
2025-04-24 7:20 ` [PATCH v13 06/28] riscv/mm : ensure PROT_WRITE leads to VM_READ | VM_WRITE Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 07/28] riscv mm: manufacture shadow stack pte Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 08/28] riscv mmu: teach pte_mkwrite to manufacture shadow stack PTEs Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 09/28] riscv mmu: write protect and shadow stack Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 10/28] riscv/mm: Implement map_shadow_stack() syscall Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 11/28] riscv/shstk: If needed allocate a new shadow stack on clone Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 12/28] riscv: Implements arch agnostic shadow stack prctls Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 13/28] prctl: arch-agnostic prctl for indirect branch tracking Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 14/28] riscv: Implements arch agnostic indirect branch tracking prctls Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 15/28] riscv/traps: Introduce software check exception Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 16/28] riscv: signal: abstract header saving for setup_sigcontext Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 17/28] riscv/signal: save and restore of shadow stack for signal Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 18/28] riscv/kernel: update __show_regs to print shadow stack register Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 19/28] riscv/ptrace: riscv cfi status and state via ptrace and in core files Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 20/28] riscv/hwprobe: zicfilp / zicfiss enumeration in hwprobe Deepak Gupta
2025-04-24 10:05 ` Miquel Sabaté Solà
2025-04-24 16:41 ` Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 21/28] riscv: kernel command line option to opt out of user cfi Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 22/28] riscv: Add Firmware Feature SBI extensions definitions Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 23/28] riscv: enable kernel access to shadow stack memory via FWFT sbi call Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 24/28] arch/riscv: compile vdso with landing pad Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 25/28] riscv: create a config for shadow stack and landing pad instr support Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 26/28] riscv: Documentation for landing pad / indirect branch tracking Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 27/28] riscv: Documentation for shadow stack on riscv Deepak Gupta
2025-04-24 7:20 ` [PATCH v13 28/28] kselftest/riscv: kselftest for user mode cfi Deepak Gupta
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=aAnnbtABLTL81uEY@debug.ba.rivosinc.com \
--to=debug@rivosinc.com \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=alexghiti@rivosinc.com \
--cc=aliceryhl@google.com \
--cc=alistair.francis@wdc.com \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=atishp@rivosinc.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=charlie@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=ebiederm@xmission.com \
--cc=evan@rivosinc.com \
--cc=gary@garyguo.net \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=jim.shu@sifive.com \
--cc=kees@kernel.org \
--cc=kito.cheng@sifive.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=richard.henderson@linaro.org \
--cc=rick.p.edgecombe@intel.com \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
--cc=vbabka@suse.cz \
--cc=x86@kernel.org \
--cc=zong.li@sifive.com \
/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;
as well as URLs for NNTP newsgroup(s).