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>
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, Deepak Gupta <debug@rivosinc.com>
Subject: [PATCH v9 23/26] riscv: create a config for shadow stack and landing pad instr support
Date: Tue, 04 Feb 2025 17:22:10 -0800 [thread overview]
Message-ID: <20250204-v5_user_cfi_series-v9-23-b37a49c5205c@rivosinc.com> (raw)
In-Reply-To: <20250204-v5_user_cfi_series-v9-0-b37a49c5205c@rivosinc.com>
This patch creates a config for shadow stack support and landing pad instr
support. Shadow stack support and landing instr support can be enabled by
selecting `CONFIG_RISCV_USER_CFI`. Selecting `CONFIG_RISCV_USER_CFI` wires
up path to enumerate CPU support and if cpu support exists, kernel will
support cpu assisted user mode cfi.
If CONFIG_RISCV_USER_CFI is selected, select `ARCH_USES_HIGH_VMA_FLAGS`,
`ARCH_HAS_USER_SHADOW_STACK` and DYNAMIC_SIGFRAME for riscv.
Signed-off-by: Deepak Gupta <debug@rivosinc.com>
---
arch/riscv/Kconfig | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index 7612c52e9b1e..0a2e50f056e8 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -250,6 +250,26 @@ config ARCH_HAS_BROKEN_DWARF5
# https://github.com/llvm/llvm-project/commit/7ffabb61a5569444b5ac9322e22e5471cc5e4a77
depends on LD_IS_LLD && LLD_VERSION < 180000
+config RISCV_USER_CFI
+ def_bool y
+ bool "riscv userspace control flow integrity"
+ depends on 64BIT && $(cc-option,-mabi=lp64 -march=rv64ima_zicfiss)
+ depends on RISCV_ALTERNATIVE
+ select ARCH_HAS_USER_SHADOW_STACK
+ select ARCH_USES_HIGH_VMA_FLAGS
+ select DYNAMIC_SIGFRAME
+ help
+ Provides CPU assisted control flow integrity to userspace tasks.
+ Control flow integrity is provided by implementing shadow stack for
+ backward edge and indirect branch tracking for forward edge in program.
+ Shadow stack protection is a hardware feature that detects function
+ return address corruption. This helps mitigate ROP attacks.
+ Indirect branch tracking enforces that all indirect branches must land
+ on a landing pad instruction else CPU will fault. This mitigates against
+ JOP / COP attacks. Applications must be enabled to use it, and old user-
+ space does not get protection "for free".
+ default y
+
config ARCH_MMAP_RND_BITS_MIN
default 18 if 64BIT
default 8
--
2.34.1
next prev parent reply other threads:[~2025-02-05 1:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 1:21 [PATCH v9 00/26] riscv control-flow integrity for usermode Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 01/26] mm: helper `is_shadow_stack_vma` to check shadow stack vma Deepak Gupta
2025-02-07 9:27 ` Vlastimil Babka
2025-02-07 20:06 ` Mark Brown
2025-02-07 22:44 ` Deepak Gupta
2025-02-07 22:44 ` Deepak Gupta
2025-02-07 23:44 ` Deepak Gupta
2025-02-07 23:52 ` Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 02/26] dt-bindings: riscv: zicfilp and zicfiss in dt-bindings (extensions.yaml) Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 03/26] riscv: zicfiss / zicfilp enumeration Deepak Gupta
2025-02-06 13:50 ` Clément Léger
2025-02-07 23:25 ` Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 04/26] riscv: zicfiss / zicfilp extension csr and bit definitions Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 05/26] riscv: usercfi state for task and save/restore of CSR_SSP on trap entry/exit Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 06/26] riscv/mm : ensure PROT_WRITE leads to VM_READ | VM_WRITE Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 07/26] riscv mm: manufacture shadow stack pte Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 08/26] riscv mmu: teach pte_mkwrite to manufacture shadow stack PTEs Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 09/26] riscv mmu: write protect and shadow stack Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 10/26] riscv/mm: Implement map_shadow_stack() syscall Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 11/26] riscv/shstk: If needed allocate a new shadow stack on clone Deepak Gupta
2025-02-05 1:21 ` [PATCH v9 12/26] riscv: Implements arch agnostic shadow stack prctls Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 13/26] prctl: arch-agnostic prctl for indirect branch tracking Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 14/26] riscv/traps: Introduce software check exception Deepak Gupta
2025-02-06 13:49 ` Clément Léger
2025-02-07 21:26 ` Deepak Gupta
2025-02-10 7:42 ` Clément Léger
2025-02-05 1:22 ` [PATCH v9 15/26] riscv: signal: abstract header saving for setup_sigcontext Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 16/26] riscv/signal: save and restore of shadow stack for signal Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 17/26] riscv/kernel: update __show_regs to print shadow stack register Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 18/26] riscv/ptrace: riscv cfi status and state via ptrace and in core files Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 19/26] riscv/hwprobe: zicfilp / zicfiss enumeration in hwprobe Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 20/26] riscv: Add Firmware Feature SBI extensions definitions Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 21/26] riscv: enable kernel access to shadow stack memory via FWFT sbi call Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 22/26] riscv: kernel command line option to opt out of user cfi Deepak Gupta
2025-02-05 1:22 ` Deepak Gupta [this message]
2025-02-05 1:22 ` [PATCH v9 24/26] riscv: Documentation for landing pad / indirect branch tracking Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 25/26] riscv: Documentation for shadow stack on riscv Deepak Gupta
2025-02-05 1:22 ` [PATCH v9 26/26] 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=20250204-v5_user_cfi_series-v9-23-b37a49c5205c@rivosinc.com \
--to=debug@rivosinc.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=alistair.francis@wdc.com \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=atishp@rivosinc.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=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=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=samitolvanen@google.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--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