From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: broonie@kernel.org
Cc: Szabolcs.Nagy@arm.com,bp@alien8.de,brauner@kernel.org,bristot@redhat.com,bsegall@google.com,catalin.marinas@arm.com,dave.hansen@linux.intel.com,david@redhat.com,debug@rivosinc.com,dietmar.eggemann@arm.com,fweimer@redhat.com,hjl.tools@gmail.com,hpa@zytor.com,jannh@google.com,juri.lelli@redhat.com,kees@kernel.org,linux-api@vger.kernel.org,linux-kernel@vger.kernel.org,linux-kselftest@vger.kernel.org,mgorman@suse.de,mingo@redhat.com,peterz@infradead.org,rick.p.edgecombe@intel.com,rostedt@goodmis.org,shuah@kernel.org,tglx@linutronix.de,vincent.guittot@linaro.org,vschneid@redhat.com,will@kernel.org,x86@kernel.org
Subject: Re: [PATCH RFT v6 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
Date: Tue, 16 Jul 2024 01:38:18 -0300 [thread overview]
Message-ID: <87ttgqt0hx.fsf@linaro.org> (raw)
In-Reply-To: <20240623-clone3-shadow-stack-v6-3-9ee7783b1fb9@kernel.org>
Hello,
> diff --git a/mm/Kconfig b/mm/Kconfig
> index b4cb45255a54..45416916dec1 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -1249,6 +1249,12 @@ config IOMMU_MM_DATA
> config EXECMEM
> bool
>
> +config ARCH_HAS_USER_SHADOW_STACK
> + bool
> + help
> + The architecture has hardware support for userspace shadow call
> + stacks (eg, x87 CET, arm64 GCS or RISC-V Zicfiss).
s/x87/x86/ ?
--
Thiago
next prev parent reply other threads:[~2024-07-16 4:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 11:23 [PATCH RFT v6 0/9] fork: Support shadow stacks in clone3() Mark Brown
2024-06-23 11:23 ` [PATCH RFT v6 1/9] Documentation: userspace-api: Add shadow stack API documentation Mark Brown
2024-06-25 22:31 ` Randy Dunlap
2024-06-23 11:23 ` [PATCH RFT v6 2/9] selftests: Provide helper header for shadow stack testing Mark Brown
2024-06-23 11:23 ` [PATCH RFT v6 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK Mark Brown
2024-07-16 4:38 ` Thiago Jung Bauermann [this message]
2024-06-23 11:23 ` [PATCH RFT v6 4/9] fork: Add shadow stack support to clone3() Mark Brown
2024-06-23 11:23 ` [PATCH RFT v6 5/9] selftests/clone3: Remove redundant flushes of output streams Mark Brown
2024-06-23 11:23 ` [PATCH RFT v6 6/9] selftests/clone3: Factor more of main loop into test_clone3() Mark Brown
2024-06-23 11:23 ` [PATCH RFT v6 7/9] selftests/clone3: Explicitly handle child exits due to signals Mark Brown
2024-06-23 11:23 ` [PATCH RFT v6 8/9] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code Mark Brown
2024-06-23 11:23 ` [PATCH RFT v6 9/9] selftests/clone3: Test shadow stack support Mark Brown
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=87ttgqt0hx.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=Szabolcs.Nagy@arm.com \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=bristot@redhat.com \
--cc=broonie@kernel.org \
--cc=bsegall@google.com \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=debug@rivosinc.com \
--cc=dietmar.eggemann@arm.com \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.