From: Christian Brauner <brauner@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Jori Koolstra <jkoolstra@xs4all.nl>,
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 11:10:09 +0100 [thread overview]
Message-ID: <20260224-karotten-wegnimmt-79410ef99aeb@brauner> (raw)
In-Reply-To: <44a2111e33631d78aded73e4b79908db6237227f.camel@kernel.org>
On Mon, Feb 23, 2026 at 10:28:24AM -0500, Jeff Layton wrote:
> On Mon, 2026-02-23 at 16:16 +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.
> >
>
> This sounds valuable, but there was recent discussion around the
> O_REGULAR flag that said that we shouldn't be adding new flags to older
> syscalls [1]. Should this only be an OPENAT2_* flag instead?
>
> [1]: https://lore.kernel.org/linux-fsdevel/20260129-siebzehn-adler-efe74ff8f1a9@brauner/
I do like restricting it to openat2() as well.
next prev parent reply other threads:[~2026-02-24 10:10 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 [this message]
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
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-karotten-wegnimmt-79410ef99aeb@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