All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/4] Implement openat2 wrapper
Date: Wed, 14 Jan 2026 19:09:59 -0600	[thread overview]
Message-ID: <1768439403-23665-1-git-send-email-mark.hatle@kernel.crashing.org> (raw)

Since openat2 isn't a regular function on most systems, the implementation
is a bit strange.  We implement the openat2 function based on the existing
openat (in the future, we may be able to get rid of openat redirecting it
to this new openat2.)  Then instead of calling real_openat2, we call
real_syscall instead.

This appears to work where I've run it, but I don't have a very extensive
test case at this time.  Any review of this serious would be appreciated.

Mark Hatle (1):
  openat2: Implement openat2 wrapper

mark.hatle (3):
  test-syscall: Remove build warning
  ports/linux/pseudo_wrappers.c: Reorder the syscall operations
  ports/linux/pseudo_wrappers.c: Call the wrappers where possible

 ports/linux/openat2/guts/openat2.c | 186 +++++++++++++++++++++++++++++++++++--
 ports/linux/pseudo_wrappers.c      |  51 ++++++----
 test/test-syscall.c                |  12 ++-
 3 files changed, 215 insertions(+), 34 deletions(-)

-- 
1.8.3.1



             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 Mark Hatle [this message]
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 ` [pseudo][PATCH 3/4] ports/linux/pseudo_wrappers.c: Call the wrappers where possible Mark Hatle
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-1-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.