All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@amd.com>
To: <yocto-patches@lists.yoctoproject.org>
Subject: [pseudo][PATCH RFC 0/2] Implement new openat2 flags
Date: Thu, 12 Nov 2026 11:47:08 -0700	[thread overview]
Message-ID: <20261112184710.549482-1-mark.hatle@amd.com> (raw)

See [YOCTO #16327].  As reported the new Linux 7.2 includes both
O_EMPTYPATH and OPENAT2_REGULAR.

OPENAT2_REGULAR requires no changes, as the flag is passed to the
kernel and no local pseudo behavior changes are required.

O_EMPTYPATH requires minor changes, and also pointed out a behavior
inconsistency with the existing implementation where a blank dir
was expanded.

I do not have a Linux 7.2 or newer environment to test this on.  This
was implementated based on description, kernel source inspection and
man pages.

Sent as an RFC as I'm not able to directly run this on a newer kernel
and validate it is working.

Any review / test would be appreciated!

Mark Hatle (2):
  ports/linux: Pass an empty openat() path to the kernel
  openat2: Look at dirfd for an empty path

 makewrappers                       |  13 +++-
 ports/linux/guts/openat.c          |  21 ++++--
 ports/linux/openat2/guts/openat2.c |  24 +++++--
 ports/linux/wrapfuncs.in           |   8 +--
 test/test-openat-emptypath.c       | 105 +++++++++++++++++++++++++++++
 test/test-openat-emptypath.sh      |  12 ++++
 6 files changed, 166 insertions(+), 17 deletions(-)
 create mode 100644 test/test-openat-emptypath.c
 create mode 100755 test/test-openat-emptypath.sh

-- 
2.34.1


             reply	other threads:[~2026-11-12 18:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 18:47 Mark Hatle [this message]
2026-11-12 18:47 ` [pseudo][PATCH RFC 1/2] ports/linux: Pass an empty openat() path to the kernel Mark Hatle
2026-11-12 18:47 ` [pseudo][PATCH RFC 2/2] openat2: Look at dirfd for an empty path 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=20261112184710.549482-1-mark.hatle@amd.com \
    --to=mark.hatle@amd.com \
    --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.