All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Marc Zyngier <maz@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Arnd Bergmann <arnd@arndb.de>, Oleg Nesterov <oleg@redhat.com>,
	Eric Biederman <ebiederm@xmission.com>,
	Kees Cook <keescook@chromium.org>, Shuah Khan <shuah@kernel.org>,
	"Rick P. Edgecombe" <rick.p.edgecombe@intel.com>,
	Deepak Gupta <debug@rivosinc.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
	"H.J. Lu" <hjl.tools@gmail.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Florian Weimer <fweimer@redhat.com>,
	Christian Brauner <brauner@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
	kvmarm@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-mm@kvack.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH v8 20/38] arm64/gcs: Ensure that new threads have a GCS
Date: Mon, 19 Feb 2024 23:02:22 -0300	[thread overview]
Message-ID: <874je399ld.fsf@linaro.org> (raw)
In-Reply-To: <20240203-arm64-gcs-v8-20-c9fec77673ef@kernel.org>


Mark Brown <broonie@kernel.org> writes:

> When a new thread is created by a thread with GCS enabled the GCS needs
> to be specified along with the regular stack.  clone3() has been
> extended to support this case, allowing userspace to explicitly specify
> the size and location of the GCS.  The specified GCS must have a valid
> GCS token at the top of the stack, as though userspace were pivoting to
> the new GCS.  This will be consumed on use.  At present we do not
> atomically consume the token, this will be addressed in a future
> revision.
>
> Unfortunately plain clone() is not extensible and existing clone3()
> users will not specify a stack so all existing code would be broken if
> we mandated specifying the stack explicitly.  For compatibility with
> these cases and also x86 (which did not initially implement clone3()
> support for shadow stacks) if no GCS is specified we will allocate one
> thread so when a thread is created which has GCS enabled allocate one
  ~~~~~~

This "thread" seems extraneous in the sentence. Remove it?

> for it.  We follow the extensively discussed x86 implementation and
> allocate min(RLIMIT_STACK, 4G).  Since the GCS only stores the call

Isn't it min(RLIMIT_STACK/2, 2G), as seen in gcs_size()? If true, this
size should also be fixed in Documentation/arch/arm64/gcs.rst.

> stack and not any variables this should be more than sufficient for most
> applications.
>
> GCSs allocated via this mechanism then it will be freed when the thread
> exits, those explicitly configured by the user will not.

I'm not sure I parsed this sentence correctly. Is it missing an "If" at
the beginning?

> +unsigned long gcs_alloc_thread_stack(struct task_struct *tsk,
> +				     const struct kernel_clone_args *args)
> +{
> +	unsigned long addr, size, gcspr_el0;
> +
> +	/* If the user specified a GCS use it. */
> +	if (args->shadow_stack_size) {
> +		if (!system_supports_gcs())
> +			return (unsigned long)ERR_PTR(-EINVAL);
> +
> +		addr = args->shadow_stack;
> +		size = args->shadow_stack_size;
> +
> +		/*
> +		 * There should be a token, there might be an end of
> +		 * stack marker.
> +		 */
> +		gcspr_el0 = addr + size - (2 * sizeof(u64));
> +		if (!gcs_consume_token(tsk, gcspr_el0)) {

Should this code validate the end of stack marker? Or doesn't it matter
whether the marker is correct or not?

> +			gcspr_el0 += sizeof(u64);
> +			if (!gcs_consume_token(tsk, gcspr_el0))
> +				return (unsigned long)ERR_PTR(-EINVAL);
> +		}
> +
> +		/* Userspace is responsible for unmapping */
> +		tsk->thread.gcspr_el0 = gcspr_el0 + sizeof(u64);
> +	} else {

-- 
Thiago

WARNING: multiple messages have this Message-ID (diff)
From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Marc Zyngier <maz@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Arnd Bergmann <arnd@arndb.de>, Oleg Nesterov <oleg@redhat.com>,
	Eric Biederman <ebiederm@xmission.com>,
	Kees Cook <keescook@chromium.org>, Shuah Khan <shuah@kernel.org>,
	"Rick P. Edgecombe" <rick.p.edgecombe@intel.com>,
	Deepak Gupta <debug@rivosinc.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
	"H.J. Lu" <hjl.tools@gmail.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Florian Weimer <fweimer@redhat.com>,
	Christian Brauner <brauner@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
	kvmarm@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-mm@kvack.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH v8 20/38] arm64/gcs: Ensure that new threads have a GCS
Date: Mon, 19 Feb 2024 23:02:22 -0300	[thread overview]
Message-ID: <874je399ld.fsf@linaro.org> (raw)
In-Reply-To: <20240203-arm64-gcs-v8-20-c9fec77673ef@kernel.org>


Mark Brown <broonie@kernel.org> writes:

> When a new thread is created by a thread with GCS enabled the GCS needs
> to be specified along with the regular stack.  clone3() has been
> extended to support this case, allowing userspace to explicitly specify
> the size and location of the GCS.  The specified GCS must have a valid
> GCS token at the top of the stack, as though userspace were pivoting to
> the new GCS.  This will be consumed on use.  At present we do not
> atomically consume the token, this will be addressed in a future
> revision.
>
> Unfortunately plain clone() is not extensible and existing clone3()
> users will not specify a stack so all existing code would be broken if
> we mandated specifying the stack explicitly.  For compatibility with
> these cases and also x86 (which did not initially implement clone3()
> support for shadow stacks) if no GCS is specified we will allocate one
> thread so when a thread is created which has GCS enabled allocate one
  ~~~~~~

This "thread" seems extraneous in the sentence. Remove it?

> for it.  We follow the extensively discussed x86 implementation and
> allocate min(RLIMIT_STACK, 4G).  Since the GCS only stores the call

Isn't it min(RLIMIT_STACK/2, 2G), as seen in gcs_size()? If true, this
size should also be fixed in Documentation/arch/arm64/gcs.rst.

> stack and not any variables this should be more than sufficient for most
> applications.
>
> GCSs allocated via this mechanism then it will be freed when the thread
> exits, those explicitly configured by the user will not.

I'm not sure I parsed this sentence correctly. Is it missing an "If" at
the beginning?

> +unsigned long gcs_alloc_thread_stack(struct task_struct *tsk,
> +				     const struct kernel_clone_args *args)
> +{
> +	unsigned long addr, size, gcspr_el0;
> +
> +	/* If the user specified a GCS use it. */
> +	if (args->shadow_stack_size) {
> +		if (!system_supports_gcs())
> +			return (unsigned long)ERR_PTR(-EINVAL);
> +
> +		addr = args->shadow_stack;
> +		size = args->shadow_stack_size;
> +
> +		/*
> +		 * There should be a token, there might be an end of
> +		 * stack marker.
> +		 */
> +		gcspr_el0 = addr + size - (2 * sizeof(u64));
> +		if (!gcs_consume_token(tsk, gcspr_el0)) {

Should this code validate the end of stack marker? Or doesn't it matter
whether the marker is correct or not?

> +			gcspr_el0 += sizeof(u64);
> +			if (!gcs_consume_token(tsk, gcspr_el0))
> +				return (unsigned long)ERR_PTR(-EINVAL);
> +		}
> +
> +		/* Userspace is responsible for unmapping */
> +		tsk->thread.gcspr_el0 = gcspr_el0 + sizeof(u64);
> +	} else {

-- 
Thiago

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Marc Zyngier <maz@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Arnd Bergmann <arnd@arndb.de>, Oleg Nesterov <oleg@redhat.com>,
	Eric Biederman <ebiederm@xmission.com>,
	Kees Cook <keescook@chromium.org>, Shuah Khan <shuah@kernel.org>,
	"Rick P. Edgecombe" <rick.p.edgecombe@intel.com>,
	Deepak Gupta <debug@rivosinc.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
	"H.J. Lu" <hjl.tools@gmail.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Florian Weimer <fweimer@redhat.com>,
	Christian Brauner <brauner@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
	kvmarm@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-mm@kvack.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH v8 20/38] arm64/gcs: Ensure that new threads have a GCS
Date: Mon, 19 Feb 2024 23:02:22 -0300	[thread overview]
Message-ID: <874je399ld.fsf@linaro.org> (raw)
In-Reply-To: <20240203-arm64-gcs-v8-20-c9fec77673ef@kernel.org>


Mark Brown <broonie@kernel.org> writes:

> When a new thread is created by a thread with GCS enabled the GCS needs
> to be specified along with the regular stack.  clone3() has been
> extended to support this case, allowing userspace to explicitly specify
> the size and location of the GCS.  The specified GCS must have a valid
> GCS token at the top of the stack, as though userspace were pivoting to
> the new GCS.  This will be consumed on use.  At present we do not
> atomically consume the token, this will be addressed in a future
> revision.
>
> Unfortunately plain clone() is not extensible and existing clone3()
> users will not specify a stack so all existing code would be broken if
> we mandated specifying the stack explicitly.  For compatibility with
> these cases and also x86 (which did not initially implement clone3()
> support for shadow stacks) if no GCS is specified we will allocate one
> thread so when a thread is created which has GCS enabled allocate one
  ~~~~~~

This "thread" seems extraneous in the sentence. Remove it?

> for it.  We follow the extensively discussed x86 implementation and
> allocate min(RLIMIT_STACK, 4G).  Since the GCS only stores the call

Isn't it min(RLIMIT_STACK/2, 2G), as seen in gcs_size()? If true, this
size should also be fixed in Documentation/arch/arm64/gcs.rst.

> stack and not any variables this should be more than sufficient for most
> applications.
>
> GCSs allocated via this mechanism then it will be freed when the thread
> exits, those explicitly configured by the user will not.

I'm not sure I parsed this sentence correctly. Is it missing an "If" at
the beginning?

> +unsigned long gcs_alloc_thread_stack(struct task_struct *tsk,
> +				     const struct kernel_clone_args *args)
> +{
> +	unsigned long addr, size, gcspr_el0;
> +
> +	/* If the user specified a GCS use it. */
> +	if (args->shadow_stack_size) {
> +		if (!system_supports_gcs())
> +			return (unsigned long)ERR_PTR(-EINVAL);
> +
> +		addr = args->shadow_stack;
> +		size = args->shadow_stack_size;
> +
> +		/*
> +		 * There should be a token, there might be an end of
> +		 * stack marker.
> +		 */
> +		gcspr_el0 = addr + size - (2 * sizeof(u64));
> +		if (!gcs_consume_token(tsk, gcspr_el0)) {

Should this code validate the end of stack marker? Or doesn't it matter
whether the marker is correct or not?

> +			gcspr_el0 += sizeof(u64);
> +			if (!gcs_consume_token(tsk, gcspr_el0))
> +				return (unsigned long)ERR_PTR(-EINVAL);
> +		}
> +
> +		/* Userspace is responsible for unmapping */
> +		tsk->thread.gcspr_el0 = gcspr_el0 + sizeof(u64);
> +	} else {

-- 
Thiago

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-02-20  2:02 UTC|newest]

Thread overview: 270+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03 12:25 [PATCH v8 00/38] arm64/gcs: Provide support for GCS in userspace Mark Brown
2024-02-03 12:25 ` Mark Brown
2024-02-03 12:25 ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 01/38] arm64/mm: Restructure arch_validate_flags() for extensibility Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 02/38] prctl: arch-agnostic prctl for shadow stack Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 03/38] mman: Add map_shadow_stack() flags Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 04/38] arm64: Document boot requirements for Guarded Control Stacks Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 05/38] arm64/gcs: Document the ABI " Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 06/38] arm64/sysreg: Add definitions for architected GCS caps Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 07/38] arm64/gcs: Add manual encodings of GCS instructions Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 08/38] arm64/gcs: Provide put_user_gcs() Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 09/38] arm64/cpufeature: Runtime detection of Guarded Control Stack (GCS) Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 10/38] arm64/mm: Allocate PIE slots for EL0 guarded control stack Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 11/38] mm: Define VM_SHADOW_STACK for arm64 when we support GCS Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 12/38] arm64/mm: Map pages for guarded control stack Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 13/38] KVM: arm64: Manage GCS registers for guests Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-05  9:46   ` Marc Zyngier
2024-02-05  9:46     ` Marc Zyngier
2024-02-05  9:46     ` Marc Zyngier
2024-02-05 12:35     ` Mark Brown
2024-02-05 12:35       ` Mark Brown
2024-02-05 12:35       ` Mark Brown
2024-02-05 15:34       ` Marc Zyngier
2024-02-05 15:34         ` Marc Zyngier
2024-02-05 15:34         ` Marc Zyngier
2024-02-05 16:58         ` Mark Brown
2024-02-05 16:58           ` Mark Brown
2024-02-05 16:58           ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 14/38] arm64/gcs: Allow GCS usage at EL0 and EL1 Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 15/38] arm64/idreg: Add overrride for GCS Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 16/38] arm64/hwcap: Add hwcap " Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 17/38] arm64/traps: Handle GCS exceptions Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 18/38] arm64/mm: Handle GCS data aborts Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 19/38] arm64/gcs: Context switch GCS state for EL0 Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 20/38] arm64/gcs: Ensure that new threads have a GCS Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-20  2:02   ` Thiago Jung Bauermann [this message]
2024-02-20  2:02     ` Thiago Jung Bauermann
2024-02-20  2:02     ` Thiago Jung Bauermann
2024-02-21 18:16     ` Mark Brown
2024-02-21 18:16       ` Mark Brown
2024-02-21 18:16       ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 21/38] arm64/gcs: Implement shadow stack prctl() interface Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 22/38] arm64/mm: Implement map_shadow_stack() Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 23/38] arm64/signal: Set up and restore the GCS context for signal handlers Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-20  2:03   ` Thiago Jung Bauermann
2024-02-20  2:03     ` Thiago Jung Bauermann
2024-02-20  2:03     ` Thiago Jung Bauermann
2024-02-03 12:25 ` [PATCH v8 24/38] arm64/signal: Expose GCS state in signal frames Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 25/38] arm64/ptrace: Expose GCS via ptrace and core files Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 26/38] arm64: Add Kconfig for Guarded Control Stack (GCS) Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 27/38] kselftest/arm64: Verify the GCS hwcap Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 28/38] kselftest/arm64: Add GCS as a detected feature in the signal tests Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 29/38] kselftest/arm64: Add framework support for GCS to signal handling tests Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 30/38] kselftest/arm64: Allow signals tests to specify an expected si_code Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 31/38] kselftest/arm64: Always run signals tests with GCS enabled Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 32/38] kselftest/arm64: Add very basic GCS test program Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25 ` [PATCH v8 33/38] kselftest/arm64: Add a GCS test program built with the system libc Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-03 12:25   ` Mark Brown
2024-02-20  2:15   ` Thiago Jung Bauermann
2024-02-20  2:15     ` Thiago Jung Bauermann
2024-02-20  2:15     ` Thiago Jung Bauermann
2024-02-21 19:20     ` Mark Brown
2024-02-21 19:20       ` Mark Brown
2024-02-21 19:20       ` Mark Brown
2024-02-22 19:11     ` Mark Brown
2024-02-22 19:11       ` Mark Brown
2024-02-22 19:11       ` Mark Brown
2024-02-23  2:24       ` Thiago Jung Bauermann
2024-02-23  2:24         ` Thiago Jung Bauermann
2024-02-23  2:24         ` Thiago Jung Bauermann
2024-02-27 16:14         ` Mark Brown
2024-02-27 16:14           ` Mark Brown
2024-02-27 16:14           ` Mark Brown
2024-02-27 19:08           ` Thiago Jung Bauermann
2024-02-27 19:08             ` Thiago Jung Bauermann
2024-02-27 19:08             ` Thiago Jung Bauermann
2024-02-29 21:45         ` Mark Brown
2024-02-29 21:45           ` Mark Brown
2024-02-29 21:45           ` Mark Brown
2024-02-29 22:13           ` Thiago Jung Bauermann
2024-02-29 22:13             ` Thiago Jung Bauermann
2024-02-29 22:13             ` Thiago Jung Bauermann
2024-02-03 12:26 ` [PATCH v8 34/38] kselftest/arm64: Add test coverage for GCS mode locking Mark Brown
2024-02-03 12:26   ` Mark Brown
2024-02-03 12:26   ` Mark Brown
2024-02-03 12:26 ` [PATCH v8 35/38] selftests/arm64: Add GCS signal tests Mark Brown
2024-02-03 12:26   ` Mark Brown
2024-02-03 12:26   ` Mark Brown
2024-02-20  2:17   ` Thiago Jung Bauermann
2024-02-20  2:17     ` Thiago Jung Bauermann
2024-02-20  2:17     ` Thiago Jung Bauermann
2024-02-03 12:26 ` [PATCH v8 36/38] kselftest/arm64: Add a GCS stress test Mark Brown
2024-02-03 12:26   ` Mark Brown
2024-02-03 12:26   ` Mark Brown
2024-02-03 12:26 ` [PATCH v8 37/38] kselftest/arm64: Enable GCS for the FP stress tests Mark Brown
2024-02-03 12:26   ` Mark Brown
2024-02-03 12:26   ` Mark Brown
2024-02-03 12:26 ` [PATCH v8 38/38] kselftest: Provide shadow stack enable helpers for arm64 Mark Brown
2024-02-03 12:26   ` Mark Brown
2024-02-03 12:26   ` Mark Brown
2024-02-20  2:00 ` [PATCH v8 00/38] arm64/gcs: Provide support for GCS in userspace Thiago Jung Bauermann
2024-02-20  2:00   ` Thiago Jung Bauermann
2024-02-20  2:00   ` Thiago Jung Bauermann
2024-02-20 16:36 ` Stefan O'Rear
2024-02-20 16:36   ` Stefan O'Rear
2024-02-20 16:36   ` Stefan O'Rear
2024-02-20 18:41   ` Edgecombe, Rick P
2024-02-20 18:41     ` Edgecombe, Rick P
2024-02-20 18:41     ` Edgecombe, Rick P
2024-02-20 18:57     ` [musl] " Rich Felker
2024-02-20 18:57       ` Rich Felker
2024-02-20 18:57       ` Rich Felker
2024-02-20 23:30       ` Edgecombe, Rick P
2024-02-20 23:30         ` Edgecombe, Rick P
2024-02-20 23:30         ` Edgecombe, Rick P
2024-02-20 23:54         ` dalias
2024-02-20 23:54           ` dalias
2024-02-20 23:54           ` dalias
2024-02-21  0:35           ` Edgecombe, Rick P
2024-02-21  0:35             ` Edgecombe, Rick P
2024-02-21  0:35             ` Edgecombe, Rick P
2024-02-21  0:44             ` Mark Brown
2024-02-21  0:44               ` Mark Brown
2024-02-21  0:44               ` Mark Brown
2024-02-21  1:27             ` dalias
2024-02-21  1:27               ` dalias
2024-02-21  1:27               ` dalias
2024-02-21  2:11               ` Edgecombe, Rick P
2024-02-21  2:11                 ` Edgecombe, Rick P
2024-02-21  2:11                 ` Edgecombe, Rick P
2024-02-21  4:18                 ` Edgecombe, Rick P
2024-02-21  4:18                   ` Edgecombe, Rick P
2024-02-21  4:18                   ` Edgecombe, Rick P
2024-02-21 13:53               ` Mark Brown
2024-02-21 13:53                 ` Mark Brown
2024-02-21 13:53                 ` Mark Brown
2024-02-21 14:58                 ` dalias
2024-02-21 14:58                   ` dalias
2024-02-21 14:58                   ` dalias
2024-02-21 17:36                   ` Mark Brown
2024-02-21 17:36                     ` Mark Brown
2024-02-21 17:36                     ` Mark Brown
2024-02-21 17:57                     ` dalias
2024-02-21 17:57                       ` dalias
2024-02-21 17:57                       ` dalias
2024-02-21 18:12                       ` Edgecombe, Rick P
2024-02-21 18:12                         ` Edgecombe, Rick P
2024-02-21 18:12                         ` Edgecombe, Rick P
2024-02-21 18:30                         ` dalias
2024-02-21 18:30                           ` dalias
2024-02-21 18:30                           ` dalias
2024-02-21 18:53                           ` Edgecombe, Rick P
2024-02-21 18:53                             ` Edgecombe, Rick P
2024-02-21 18:53                             ` Edgecombe, Rick P
2024-02-21 19:06                             ` dalias
2024-02-21 19:06                               ` dalias
2024-02-21 19:06                               ` dalias
2024-02-21 19:22                               ` Edgecombe, Rick P
2024-02-21 19:22                                 ` Edgecombe, Rick P
2024-02-21 19:22                                 ` Edgecombe, Rick P
2024-02-21 20:18                                 ` dalias
2024-02-21 20:18                                   ` dalias
2024-02-21 20:18                                   ` dalias
2024-02-21 20:18                                 ` H.J. Lu
2024-02-21 20:18                                   ` H.J. Lu
2024-02-21 20:18                                   ` H.J. Lu
2024-02-21 20:25                                   ` H.J. Lu
2024-02-21 20:25                                     ` H.J. Lu
2024-02-21 20:25                                     ` H.J. Lu
2024-02-21 21:12                                     ` H.J. Lu
2024-02-21 21:12                                       ` H.J. Lu
2024-02-21 21:12                                       ` H.J. Lu
2024-02-22 13:57                                 ` Mark Brown
2024-02-22 13:57                                   ` Mark Brown
2024-02-22 13:57                                   ` Mark Brown
2024-02-21 18:32                       ` Mark Brown
2024-02-21 18:32                         ` Mark Brown
2024-02-21 18:32                         ` Mark Brown
2024-02-21 19:10                         ` dalias
2024-02-21 19:10                           ` dalias
2024-02-21 19:10                           ` dalias
2024-03-02 14:57                     ` Szabolcs Nagy
2024-03-02 14:57                       ` Szabolcs Nagy
2024-03-02 14:57                       ` Szabolcs Nagy
2024-03-02 15:05                       ` H.J. Lu
2024-03-02 15:05                         ` H.J. Lu
2024-03-02 15:05                         ` H.J. Lu
2024-03-14 14:03                       ` Mark Brown
2024-03-14 14:03                         ` Mark Brown
2024-03-14 14:03                         ` Mark Brown
2024-02-20 23:59         ` Stefan O'Rear
2024-02-20 23:59           ` Stefan O'Rear
2024-02-20 23:59           ` Stefan O'Rear
2024-02-21  0:40           ` Mark Brown
2024-02-21  0:40             ` Mark Brown
2024-02-21  0:40             ` Mark Brown
2024-02-21  4:30           ` Edgecombe, Rick P
2024-02-21  4:30             ` Edgecombe, Rick P
2024-02-21  4:30             ` Edgecombe, Rick P
2024-02-20 20:14     ` Mark Brown
2024-02-20 20:14       ` Mark Brown
2024-02-20 20:14       ` Mark Brown
2024-02-20 23:30       ` Edgecombe, Rick P
2024-02-20 23:30         ` Edgecombe, Rick P
2024-02-20 23:30         ` Edgecombe, Rick P

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=874je399ld.fsf@linaro.org \
    --to=thiago.bauermann@linaro.org \
    --cc=Szabolcs.Nagy@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=brauner@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=debug@rivosinc.com \
    --cc=ebiederm@xmission.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=james.morse@arm.com \
    --cc=keescook@chromium.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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=maz@kernel.org \
    --cc=oleg@redhat.com \
    --cc=oliver.upton@linux.dev \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=shuah@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=will@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.