From: David Howells <dhowells@redhat.com>
To: Christian Brauner <brauner@kernel.org>
Cc: dhowells@redhat.com, Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <christian@brauner.io>,
Marc Dionne <marc.dionne@auristor.com>,
Jeffrey Altman <jaltman@auristor.com>,
Steve French <sfrench@samba.org>,
linux-afs@lists.infradead.org, openafs-devel@openafs.org,
linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] vfs, afs, bash: Fix miscomparison of foreign user IDs in the VFS
Date: Wed, 12 Aug 2026 14:07:56 +0100 [thread overview]
Message-ID: <986590.1786540076@warthog.procyon.org.uk> (raw)
In-Reply-To: <20260810-jazzfest-unglaubhaft-miene-4d1cf4cf42d3@brauner>
Christian Brauner <brauner@kernel.org> wrote:
> > Note that chown may also need modifying in some way - but that can't
> > necessarily supply the information required (for instance, an AuriStor YFS
> > ID is 64 bits, but chown can only handle a 32-bit integer; CIFS might use
> > a GUID).
>
> Seems that some other changes are required for this. I'll take a look
> once a new version is out.
If you're referring to the chown thing, can we ignore that for now? It would
probably need some sort of new system call, but I don't know how that should
look for now.
David
prev parent reply other threads:[~2026-08-12 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 14:13 [PATCH v3 0/2] vfs, afs, bash: Fix miscomparison of foreign user IDs in the VFS David Howells
2026-07-28 14:13 ` [PATCH v3 1/2] vfs: Allow filesystems with foreign owner IDs to override UID checks David Howells
2026-07-30 23:35 ` Mimi Zohar
2026-08-12 13:12 ` David Howells
2026-07-28 14:13 ` [PATCH v3 2/2] afs, bash: Fix open(O_CREAT) on an extant AFS file in a sticky dir David Howells
2026-07-30 10:46 ` Marc Dionne
2026-08-10 13:24 ` [PATCH v3 0/2] vfs, afs, bash: Fix miscomparison of foreign user IDs in the VFS Christian Brauner
2026-08-12 13:07 ` David Howells [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=986590.1786540076@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=brauner@kernel.org \
--cc=christian@brauner.io \
--cc=jaltman@auristor.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=openafs-devel@openafs.org \
--cc=sfrench@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.