From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: yocto-patches@lists.yoctoproject.org
Cc: seebs@seebs.net, richard.purdie@linuxfoundation.org
Subject: [pseudo][PATCH 3/4] ports/linux/pseudo_wrappers.c: Call the wrappers where possible
Date: Wed, 14 Jan 2026 19:10:02 -0600 [thread overview]
Message-ID: <1768439403-23665-4-git-send-email-mark.hatle@kernel.crashing.org> (raw)
In-Reply-To: <1768439403-23665-1-git-send-email-mark.hatle@kernel.crashing.org>
From: "mark.hatle" <mark.hatle@kernel.crashing.org>
Using va args, call the wrapper when the syscall is invoked. This will
allow us to implement the renameat2 and openat2 functions in the future
while keeping the syscall work unchanged.
The syscall -> wrappers should continue to be sparse into things we know
are outliers, as this could result in some maintenance work keeping the
argument processing sane.
Signed-off-by: mark.hatle <mark.hatle@kernel.crashing.org>
---
ports/linux/pseudo_wrappers.c | 29 +++++++++++++++++------------
1 file changed, 17 insertions(+), 12 deletions(-)
diff --git a/ports/linux/pseudo_wrappers.c b/ports/linux/pseudo_wrappers.c
index b486c34..7c025ae 100644
--- a/ports/linux/pseudo_wrappers.c
+++ b/ports/linux/pseudo_wrappers.c
@@ -84,26 +84,31 @@ syscall(long number, ...) {
}
#ifdef SYS_openat2
- /* concerns exist about trying to parse arguments because syscall(2)
- * specifies strange ABI behaviors. If we can get better clarity on
- * that, it could make sense to redirect to wrap_openat2().
- * There is a CVE patch (CVE-2025-45582) to tar 1.34 in Centos Stream which
+ /* There is a CVE patch (CVE-2025-45582) to tar 1.34 in Centos Stream which
* uses syscall to access openat2() and breaks builds if we don't redirect.
*/
if (number == SYS_openat2) {
- errno = ENOSYS;
- return -1;
+ va_start(ap, number);
+ int dirfd = va_arg(ap, int);
+ const char * path = va_arg(ap, const char *);
+ void *how = va_arg(ap, void *);
+ size_t size = va_arg(ap, size_t);
+
+ return wrap_openat2(dirfd, path, how, size);
}
#endif
#ifdef SYS_renameat2
- /* concerns exist about trying to parse arguments because syscall(2)
- * specifies strange ABI behaviors. If we can get better clarity on
- * that, it could make sense to redirect to wrap_renameat2().
- */
+ /* Call out wrapper, expanding the variable arguments first */
if (number == SYS_renameat2) {
- errno = ENOSYS;
- return -1;
+ va_start(ap, number);
+ int olddirfd = va_arg(ap, int);
+ const char * oldpath = va_arg(ap, const char *);
+ int newdirfd = va_arg(ap, int);
+ const char * newpath = va_arg(ap, const char *);
+ unsigned int flags = va_arg(ap, unsigned int);
+
+ return wrap_renameat2(olddirfd, oldpath, newdirfd, newpath, flags);
}
#endif
--
1.8.3.1
next prev parent reply other threads:[~2026-01-15 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 1:09 [pseudo][PATCH 0/4] Implement openat2 wrapper Mark Hatle
2026-01-15 1:10 ` [pseudo][PATCH 1/4] test-syscall: Remove build warning Mark Hatle
2026-01-15 1:10 ` [pseudo][PATCH 2/4] ports/linux/pseudo_wrappers.c: Reorder the syscall operations Mark Hatle
2026-01-15 1:10 ` Mark Hatle [this message]
2026-01-15 1:10 ` [pseudo][PATCH 4/4] openat2: Implement openat2 wrapper Mark Hatle
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=1768439403-23665-4-git-send-email-mark.hatle@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=seebs@seebs.net \
--cc=yocto-patches@lists.yoctoproject.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.