From: Jori Koolstra <jkoolstra@xs4all.nl>
To: Christian Brauner <brauner@kernel.org>
Cc: Dorjoy Chowdhury <dorjoychy111@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, ceph-devel@vger.kernel.org,
gfs2@lists.linux.dev, linux-nfs@vger.kernel.org,
linux-cifs@vger.kernel.org, v9fs@lists.linux.dev,
linux-kselftest@vger.kernel.org, viro@zeniv.linux.org.uk,
jack@suse.cz, jlayton@kernel.org, chuck.lever@oracle.com,
alex.aring@gmail.com, arnd@arndb.de, adilger@dilger.ca,
mjguzik@gmail.com, smfrench@gmail.com,
richard.henderson@linaro.org, mattst88@gmail.com,
linmag7@gmail.com, tsbogend@alpha.franken.de,
James.Bottomley@hansenpartnership.com, deller@gmx.de,
davem@davemloft.net, andreas@gaisler.com, idryomov@gmail.com,
amarkuze@redhat.com, slava@dubeyko.com, agruenba@redhat.com,
trondmy@kernel.org, anna@kernel.org, sfrench@samba.org,
pc@manguebit.org, ronniesahlberg@gmail.com,
sprasad@microsoft.com, tom@talpey.com, bharathsm@microsoft.com,
shuah@kernel.org, miklos@szeredi.hu, hansg@kernel.org,
Aleksa Sarai <cyphar@cyphar.com>
Subject: Re: [PATCH v6 1/4] openat2: new OPENAT2_REGULAR flag support
Date: Thu, 16 Apr 2026 23:36:31 +0200 (CEST) [thread overview]
Message-ID: <850388882.378351.1776375391778@kpc.webmail.kpnmail.nl> (raw)
In-Reply-To: <20260416-aufbau-sorgenfrei-cfa87c9ddc11@brauner>
> Op 16-04-2026 17:15 CEST schreef Christian Brauner <brauner@kernel.org>:
>
>
> On Thu, Apr 16, 2026 at 05:03:26PM +0200, Jori Koolstra wrote:
> >
> > If I recall correctly, Aleksa has suggested we might also want to add
> > O_EMPTYPATH to openat() instead of only allowing this for openat2().
> > I am waiting to see what Christian thinks of this.
>
> We can do that, yes. For O_EMPTYPATH that is workable.
All right, then I'll update the patch this weekend.
>
> I don't mind too much if we leave OPENAT2_REGUALR in the 32-bit flag
> space. It'll silently be ignored but the flag name should give it away.
I would also prefer to have the bits separated. Although it is unlikely
that we will add so many O_* that we will ever run out of space, it just
seems cleaner, and at no cost. But it's not too important.
Thanks,
Jori.
next prev parent reply other threads:[~2026-04-16 21:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 17:22 [PATCH v6 0/4] OPENAT2_REGULAR flag support for openat2 Dorjoy Chowdhury
2026-03-28 17:22 ` [PATCH v6 1/4] openat2: new OPENAT2_REGULAR flag support Dorjoy Chowdhury
2026-03-30 11:49 ` Jeff Layton
2026-03-30 15:07 ` Dorjoy Chowdhury
2026-04-01 19:02 ` Jeff Layton
2026-04-04 15:17 ` Dorjoy Chowdhury
2026-04-05 23:27 ` Jeff Layton
2026-04-06 15:30 ` Dorjoy Chowdhury
2026-04-14 17:33 ` Dorjoy Chowdhury
2026-04-16 11:41 ` Aleksa Sarai
2026-04-16 11:58 ` Dorjoy Chowdhury
2026-04-16 13:05 ` Aleksa Sarai
2026-04-16 13:28 ` Jeff Layton
2026-04-16 13:52 ` Jori Koolstra
2026-04-16 14:21 ` Dorjoy Chowdhury
2026-04-16 15:03 ` Jori Koolstra
2026-04-16 15:15 ` Christian Brauner
2026-04-16 21:36 ` Jori Koolstra [this message]
2026-04-16 15:15 ` Aleksa Sarai
2026-04-16 21:42 ` Jori Koolstra
2026-04-17 7:58 ` Aleksa Sarai
2026-04-27 13:27 ` Florian Weimer
2026-04-27 14:17 ` Dorjoy Chowdhury
2026-04-27 14:29 ` Christian Brauner
2026-03-28 17:22 ` [PATCH v6 2/4] kselftest/openat2: test for OPENAT2_REGULAR flag Dorjoy Chowdhury
2026-03-28 17:22 ` [PATCH v6 3/4] sparc/fcntl.h: convert O_* flag macros from hex to octal Dorjoy Chowdhury
2026-03-28 17:22 ` [PATCH v6 4/4] mips/fcntl.h: " Dorjoy Chowdhury
2026-04-16 13:07 ` [PATCH v6 0/4] OPENAT2_REGULAR flag support for openat2 Christian Brauner
2026-04-16 15:22 ` Dorjoy Chowdhury
2026-04-20 13:20 ` Christian Brauner
2026-04-20 14:31 ` Dorjoy Chowdhury
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=850388882.378351.1776375391778@kpc.webmail.kpnmail.nl \
--to=jkoolstra@xs4all.nl \
--cc=James.Bottomley@hansenpartnership.com \
--cc=adilger@dilger.ca \
--cc=agruenba@redhat.com \
--cc=alex.aring@gmail.com \
--cc=amarkuze@redhat.com \
--cc=andreas@gaisler.com \
--cc=anna@kernel.org \
--cc=arnd@arndb.de \
--cc=bharathsm@microsoft.com \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=chuck.lever@oracle.com \
--cc=cyphar@cyphar.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=dorjoychy111@gmail.com \
--cc=gfs2@lists.linux.dev \
--cc=hansg@kernel.org \
--cc=idryomov@gmail.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linmag7@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=miklos@szeredi.hu \
--cc=mjguzik@gmail.com \
--cc=pc@manguebit.org \
--cc=richard.henderson@linaro.org \
--cc=ronniesahlberg@gmail.com \
--cc=sfrench@samba.org \
--cc=shuah@kernel.org \
--cc=slava@dubeyko.com \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.com \
--cc=trondmy@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=v9fs@lists.linux.dev \
--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