From: Christian Brauner <brauner@kernel.org>
To: Jori Koolstra <jkoolstra@xs4all.nl>
Cc: jlayton@kernel.org, chuck.lever@oracle.com, alex.aring@gmail.com,
viro@zeniv.linux.org.uk, jack@suse.cz, arnd@arndb.de,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] Add support for empty path in openat and openat2 syscalls
Date: Tue, 24 Feb 2026 10:30:29 +0100 [thread overview]
Message-ID: <20260224-vorfuhr-spitzen-783550d623a2@brauner> (raw)
In-Reply-To: <20260223151652.582048-1-jkoolstra@xs4all.nl>
On Mon, Feb 23, 2026 at 04:16:52PM +0100, Jori Koolstra wrote:
> To get an operable version of an O_PATH file descriptors, it is possible
> to use openat(fd, ".", O_DIRECTORY) for directories, but other files
> currently require going through open("/proc/<pid>/fd/<nr>") which
> depends on a functioning procfs.
>
> This patch adds the O_EMPTY_PATH flag to openat and openat2. If passed
> LOOKUP_EMPTY is set at path resolve time.
>
> Signed-off-by: Jori Koolstra <jkoolstra@xs4all.nl>
> ---
Out of curiosity, did you pick this taken from our uapi-group list?
https://github.com/uapi-group/kernel-features?tab=readme-ov-file#at_empty_path-support-for-openat-and-openat2
https://github.com/uapi-group/kernel-features/issues/47
?
next prev parent reply other threads:[~2026-02-24 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 15:16 [PATCH] Add support for empty path in openat and openat2 syscalls Jori Koolstra
2026-02-23 15:28 ` Jeff Layton
2026-02-24 10:10 ` Christian Brauner
2026-02-24 13:35 ` Jori Koolstra
2026-02-24 14:31 ` Christian Brauner
2026-02-23 16:32 ` kernel test robot
2026-02-23 16:45 ` David Laight
2026-02-24 9:30 ` Christian Brauner [this message]
2026-02-24 13:33 ` Jori Koolstra
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=20260224-vorfuhr-spitzen-783550d623a2@brauner \
--to=brauner@kernel.org \
--cc=alex.aring@gmail.com \
--cc=arnd@arndb.de \
--cc=chuck.lever@oracle.com \
--cc=jack@suse.cz \
--cc=jkoolstra@xs4all.nl \
--cc=jlayton@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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