From: David Mulder <dmulder@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-cifs@vger.kernel.org
Subject: Re: 128 bit uid/gid (UUID) possible?
Date: Thu, 25 Apr 2024 13:23:41 -0600 [thread overview]
Message-ID: <f15d2f5f-2e17-42d1-a376-3272b4460e37@suse.com> (raw)
In-Reply-To: <CAHk-=wiaWr2fsvMx3EWdXRegQ9Fo5VzhRFn7cmLDErh1jhos9g@mail.gmail.com>
On 4/25/24 1:21 PM, Linus Torvalds wrote:
> On Thu, 25 Apr 2024 at 12:17, David Mulder <dmulder@suse.com> wrote:
>> What is the possibility of increasing the uid/gid size in the kernel from 32bits to 128bits?
> Nope.
>
> We don't have user-space interfaces for it (st_uid is 32-bit), and the
> pain is not worth any theoretical gain.
>
> Linus
Ok, thanks. I'll move forward with id mapping.
--
David Mulder
Labs Software Engineer, Samba
SUSE
1221 S Valley Grove Way, Suite 500
Pleasant Grove, UT 84062
(P)+1 385.208.2989
dmulder@suse.com
http://www.suse.com
prev parent reply other threads:[~2024-04-25 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 9:53 128 bit uid/gid (UUID) possible? David Mulder
[not found] ` <54d8dccd-f224-4ad6-875c-774c45f9ba9b@suse.com>
2024-04-25 19:21 ` Linus Torvalds
2024-04-25 19:23 ` David Mulder [this message]
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=f15d2f5f-2e17-42d1-a376-3272b4460e37@suse.com \
--to=dmulder@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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