public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/arm/gcs] aarch64: Add GCS support to vfork
Date: Wed, 14 Feb 2024 15:06:43 +0000 (GMT) [thread overview]
Message-ID: <20240214150643.0ED2C385C422@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=868c129b90a52f7c30b8a560dc580f851db4b6fc
commit 868c129b90a52f7c30b8a560dc580f851db4b6fc
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Wed Dec 27 18:36:10 2023 +0000
aarch64: Add GCS support to vfork
Diff:
---
sysdeps/unix/sysv/linux/aarch64/vfork.S | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/sysdeps/unix/sysv/linux/aarch64/vfork.S b/sysdeps/unix/sysv/linux/aarch64/vfork.S
index e71e492da3..cfaf4a1ffb 100644
--- a/sysdeps/unix/sysv/linux/aarch64/vfork.S
+++ b/sysdeps/unix/sysv/linux/aarch64/vfork.S
@@ -33,8 +33,14 @@ ENTRY (__vfork)
cmn x0, #4095
b.cs .Lsyscall_error
+ cbz x0, L(child)
RET
-
+L(child):
+ /* Return with indirect branch in the child to support GCS.
+ Clear x30 to crash early if the child tries to ret. */
+ mov x1, x30
+ mov x30, 0
+ br x1
PSEUDO_END (__vfork)
libc_hidden_def (__vfork)
reply other threads:[~2024-02-14 15:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240214150643.0ED2C385C422@sourceware.org \
--to=nsz@sourceware.org \
--cc=glibc-cvs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).