From: Florian Weimer <fweimer@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
David Howells <dhowells@redhat.com>, DJ Delorie <dj@redhat.com>
Subject: O_CLOEXEC use for OPEN_TREE_CLOEXEC
Date: Tue, 13 Jan 2026 23:40:55 +0100 [thread overview]
Message-ID: <lhupl7dcf0o.fsf@oldenburg.str.redhat.com> (raw)
In <linux/mount.h>, we have this:
#define OPEN_TREE_CLOEXEC O_CLOEXEC /* Close the file on execve() */
This causes a few pain points for us to on the glibc side when we mirror
this into <linux/mount.h> becuse O_CLOEXEC is defined in <fcntl.h>,
which is one of the headers that's completely incompatible with the UAPI
headers.
The reason why this is painful is because O_CLOEXEC has at least three
different values across architectures: 0x80000, 0x200000, 0x400000
Even for the UAPI this isn't ideal because it effectively burns three
open_tree flags, unless the flags are made architecture-specific, too.
Thanks,
Florian
next reply other threads:[~2026-01-13 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 22:40 Florian Weimer [this message]
2026-01-14 16:03 ` O_CLOEXEC use for OPEN_TREE_CLOEXEC Christian Brauner
2026-01-14 19:42 ` Andy Lutomirski
2026-01-14 21:18 ` Aleksa Sarai
2026-01-15 8:55 ` Florian Weimer
2026-01-16 10:00 ` Christian Brauner
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=lhupl7dcf0o.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=dhowells@redhat.com \
--cc=dj@redhat.com \
--cc=linux-api@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