From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Rick P. Edgecombe" <rick.p.edgecombe@intel.com>,
Deepak Gupta <debug@rivosinc.com>,
Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
Florian Weimer <fweimer@redhat.com>,
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>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Christian Brauner <brauner@kernel.org>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, Will Deacon <will@kernel.org>,
jannh@google.com, Yury Khrustalev <yury.khrustalev@arm.com>,
Wilco Dijkstra <wilco.dijkstra@arm.com>,
linux-kselftest@vger.kernel.org, linux-api@vger.kernel.org,
Kees Cook <kees@kernel.org>
Subject: Re: [PATCH RFT v12 1/8] arm64/gcs: Return a success value from gcs_alloc_thread_stack()
Date: Fri, 1 Nov 2024 17:40:10 +0000 [thread overview]
Message-ID: <ZyUSesV2rj5-BWYn@arm.com> (raw)
In-Reply-To: <20241031-clone3-shadow-stack-v12-1-7183eb8bee17@kernel.org>
On Thu, Oct 31, 2024 at 07:25:02PM +0000, Mark Brown wrote:
> Currently as a result of templating from x86 code gcs_alloc_thread_stack()
> returns a pointer as an unsigned int however on arm64 we don't actually use
> this pointer value as anything other than a pass/fail flag. Simplify the
> interface to just return an int with 0 on success and a negative error code
> on failure.
>
> Acked-by: Deepak Gupta <debug@rivosinc.com>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2024-11-01 17:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 19:25 [PATCH RFT v12 0/8] fork: Support shadow stacks in clone3() Mark Brown
2024-10-31 19:25 ` [PATCH RFT v12 1/8] arm64/gcs: Return a success value from gcs_alloc_thread_stack() Mark Brown
2024-11-01 17:40 ` Catalin Marinas [this message]
2024-10-31 19:25 ` [PATCH RFT v12 2/8] Documentation: userspace-api: Add shadow stack API documentation Mark Brown
2024-11-29 16:18 ` Yury Khrustalev
2024-10-31 19:25 ` [PATCH RFT v12 3/8] selftests: Provide helper header for shadow stack testing Mark Brown
2024-10-31 19:25 ` [PATCH RFT v12 4/8] fork: Add shadow stack support to clone3() Mark Brown
2024-11-29 16:57 ` Yury Khrustalev
2024-10-31 19:25 ` [PATCH RFT v12 5/8] selftests/clone3: Remove redundant flushes of output streams Mark Brown
2024-10-31 19:25 ` [PATCH RFT v12 6/8] selftests/clone3: Factor more of main loop into test_clone3() Mark Brown
2024-10-31 19:25 ` [PATCH RFT v12 7/8] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code Mark Brown
2024-10-31 19:25 ` [PATCH RFT v12 8/8] selftests/clone3: Test shadow stack support Mark Brown
2024-10-31 21:06 ` [PATCH RFT v12 0/8] fork: Support shadow stacks in clone3() Edgecombe, Rick P
2024-11-01 12:30 ` Mark Brown
2024-11-01 22:45 ` 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=ZyUSesV2rj5-BWYn@arm.com \
--to=catalin.marinas@arm.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=bsegall@google.com \
--cc=dave.hansen@linux.intel.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=wilco.dijkstra@arm.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yury.khrustalev@arm.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 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.