[UNIX extentions] uid/gid 64-bit

[Steven French]

cifs vfs takes the Uid and Gid from the query and converts from little 
endian and tries to stuff it in the uid_t sized field in the local 
client's inode.   For most architectures in Linux uid_t is  kernel_uid32_t 
 ie 32 bits.

For set we normally use -1 (__u64) to ask the server to use the default 
uid/gid they choose - or if setuids was specified on mount cifs (which is 
not the default) is take the fsuid and fsgid (which are normally the same 
as uid and gid) and send those


Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: 512-838-2294
email: sfrench at-sign us dot ibm dot com



"Stefan (metze) Metzmacher" <metze at samba.org> 
06/12/2006 08:52 AM

To
Multiple recipients of list SAMBA-TECHNICAL <samba-technical at samba.org>, 
sfrench at samba.org
cc

Subject
Re: [UNIX extentions] uid/gid 64-bit






-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan (metze) Metzmacher schrieb:
> Stefan (metze) Metzmacher schrieb:
>>> Hi *,
>>>
>>> I just noticed that we define SMB_UID_NO_CHANGE to 0x00000000FFFFFFFF
>>> in samba3 and samba4, shouldn't that be 0xFFFFFFFFFFFFFFFF for
>>> UNIX_INFO_BASIC?
>>>
>>> (or maybe SMB_UID_NO_CHANGE_HI 0xFFFFFFFF SMBUID_NO_CHANGE_LO 
0xFFFFFFFF
>>> for samba3)
> 
> The main problem is that the current samba3 client sends only 32 bit
> values and the rest is zeroed.
> 
> what clients are out there other than samba3?

the linux cifsfs seems to use 64 bit values in the FILE_UNIX_BASIC_INFO
struct, but doesn't use it with the no change values.

steve: is that correct?

metze
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFEjXGOm70gjA5TCD8RAm/tAJ0R81YNYELk1mV+vZo/NKZg2OGJ9QCggz3h
8eEXv3x+Mopqsd9//km+MZA=
=m0Zq
-----END PGP SIGNATURE-----