From: Eric Biggers <ebiggers@kernel.org>
To: Jan Koester <jan.koester@gmx.net>
Cc: Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
"Serge E. Hallyn" <serge@hallyn.com>, Jan Kara <jack@suse.cz>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Paul Moore <paul@paul-moore.com>, Arnd Bergmann <arnd@arndb.de>,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-arch@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-cifs@vger.kernel.org,
netdev@vger.kernel.org, audit@vger.kernel.org,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 09/41] uidgid: let kuid_t and kgid_t hold a UUID or a GUID
Date: Sun, 18 Oct 2026 14:02:22 -0700 [thread overview]
Message-ID: <20261018210222.GA9623@quark> (raw)
In-Reply-To: <9c17a1f7f82b953e6f4d9e17f4ca19d5220d7f2b.1792346472.git.jan.koester@gmx.net>
On Sun, Oct 18, 2026 at 08:01:30PM +0200, Jan Koester wrote:
> Make kuid_t and kgid_t (and vfsuid_t and vfsgid_t, which share their
> layout) tagged unions: a classic 32 bit id, an RFC 9562 UUID, or a
> Microsoft GUID. KID_LEGACY is 0, so zeroed memory still holds the root
> ids, and KUIDT_INIT()/KGIDT_INIT() keep building classic ids, so the
> bulk of the kernel needs no change. The member is renamed from val to
> legacy so the compiler finds code that peeks at it directly.
Most Linux systems aren't going to want this bloat to the core uid and
gid types. So if this is supported at all (unclear it's worth it...),
it will need to be controlled by a default-off kconfig option.
Side note: the subject line says the series contains 41 patches, but it
seems only 11 were actually sent.
- Eric
next prev parent reply other threads:[~2026-10-18 21:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 18:01 [RFC PATCH 00/41] UUID and GUID user and group ids (*_r system calls) Jan Koester
2026-10-18 18:01 ` [RFC PATCH 01/41] uuid: move uuid_t and guid_t into <linux/uuid_types.h> Jan Koester
2026-10-18 18:01 ` [RFC PATCH 02/41] uapi: add <linux/uidgid_r.h> for 128 bit capable user and group ids Jan Koester
2026-10-18 18:01 ` [RFC PATCH 03/41] uidgid: add uid_is_legacy() and gid_is_legacy() Jan Koester
2026-10-18 18:01 ` [RFC PATCH 04/41] net: sock: read sk_uid through a seqcount Jan Koester
2026-10-18 18:01 ` [RFC PATCH 05/41] af_unix: keep sender ids in skb->cb only when they are classic ids Jan Koester
2026-10-18 18:01 ` [RFC PATCH 06/41] netlink: keep classic sender ids in skb->cb Jan Koester
2026-10-18 18:01 ` [RFC PATCH 07/41] Bluetooth: " Jan Koester
2026-10-18 18:01 ` [RFC PATCH 08/41] smb: client: use __kuid_val() for the unix SIDs of the caller Jan Koester
2026-10-18 18:01 ` [RFC PATCH 09/41] uidgid: let kuid_t and kgid_t hold a UUID or a GUID Jan Koester
2026-10-18 19:47 ` Andy Lutomirski
2026-10-18 21:02 ` Eric Biggers [this message]
2026-10-19 2:10 ` Jan Koester
2026-10-18 18:01 ` [RFC PATCH 10/41] uidgid: convert between kernel ids and the ids of the *_r system calls Jan Koester
2026-10-18 18:01 ` [RFC PATCH 11/41] fscrypt: show the whole uid in the description of user key claims Jan Koester
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=20261018210222.GA9623@quark \
--to=ebiggers@kernel.org \
--cc=arnd@arndb.de \
--cc=audit@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jan.koester@gmx.net \
--cc=keyrings@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=tytso@mit.edu \
--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