From: "Pali Rohár" <pali@kernel.org>
To: Jeremy Allison <jra@samba.org>
Cc: ronnie sahlberg <ronniesahlberg@gmail.com>,
Steve French <sfrench@samba.org>,
Paulo Alcantara <pc@manguebit.com>,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: Fix getting reparse points from server without WSL support
Date: Tue, 17 Sep 2024 22:59:50 +0200 [thread overview]
Message-ID: <20240917205950.dvxvs6tghrffo336@pali> (raw)
In-Reply-To: <ZunqmhGHniR/4a9d@jeremy-rocky-laptop.localdomain>
On Tuesday 17 September 2024 13:46:18 Jeremy Allison wrote:
> On Wed, Sep 18, 2024 at 06:44:39AM +1000, ronnie sahlberg wrote:
> > On Wed, 18 Sept 2024 at 06:37, Pali Rohár <pali@kernel.org> wrote:
> > >
> > > Ok. But then I do not understand why Linux client parses and uses uid
> > > and gids which are sent over the wire. If you are saying that the SIDs
> > > must be the only source of truth then Linux client should rather ignore
> > > uid and gid values?
> >
> > What I think Jeremy is refering to is that mixing uids and sids in the
> > protocol itself is
> > a protocol design mistake.
> > Because this means that some PDUs in the protocol operate on SIDs but
> > others operate on
> > UID/GIDs and this means there is great risk of mistakes and have the
> > sid<->uid mapping return
> > different results depending on the actual PDU.
> >
> > Sometimes the sid<->uid mapping happens in the server, at other times
> > the mapping happens in the client
> > and it is very difficult to guarantee that the mapping is consistent
> > across PDUs in the protocol
> > as well as across different clients.
>
> Thanks Ronnie. You said that much better than I did :-) :-).
Understood, thank you!
So based on this for me it looks like that for client it would be safer
to ignore uid an gid for reparse points and use only SIDs.
I hope that somebody will recheck that client code in wsl_to_fattr() function.
next prev parent reply other threads:[~2024-09-17 20:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 20:02 Pali Rohár
2024-09-13 20:10 ` Pali Rohár
2024-09-17 20:06 ` Pali Rohár
2024-09-17 20:23 ` Jeremy Allison
2024-09-17 20:29 ` Pali Rohár
2024-09-17 20:31 ` Jeremy Allison
2024-09-17 20:34 ` Pali Rohár
2024-09-17 20:44 ` Jeremy Allison
2024-09-17 20:44 ` ronnie sahlberg
2024-09-17 20:46 ` Jeremy Allison
2024-09-17 20:59 ` Pali Rohár [this message]
2024-09-17 21:19 ` Steve French
2025-08-11 10:52 ` Do not use UID and GID from EAs Pali Rohár
2025-08-29 13:01 ` Pali Rohár
2024-09-17 21:04 ` [PATCH] cifs: Fix getting reparse points from server without WSL support Paulo Alcantara
2024-09-17 21:07 ` Pali Rohár
2024-09-17 21:17 ` Paulo Alcantara
2024-09-23 18:10 ` Pali Rohár
2024-10-06 10:08 ` Pali Rohár
2024-09-17 21:14 ` Steve French
2024-09-28 14:09 ` Pali Rohár
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=20240917205950.dvxvs6tghrffo336@pali \
--to=pali@kernel.org \
--cc=jra@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=ronniesahlberg@gmail.com \
--cc=sfrench@samba.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
all inboxes | Powered by JetHome®