On Dec 21, 2009, at 6:44 PM, Bart Smaalders wrote: > Lisa Week wrote: >> On Dec 21, 2009, at 3:57 PM, Bart Smaalders wrote: >>> Tim Haley wrote: >>>> I am sponsoring the following fast-track for Lisa Week. It >>>> introduces >>>> a new reserved uid and gid for purposes of improved ACL >>>> manipulation >>>> when an id is not mappable by the client or server. Requested >>>> binding >>>> is patch/micro. Timeout is 1/6/2010. >>> >>> Do the client and server exchange the unknown user id numerically or >>> via a string? If a string, does fixing the userid matter, or is >>> it the >>> name that's important? >> With NFSv4 the unknown user is exchanged via a string. You will >> see the user go over the wire looking something like >> "unknown at sun.com". (Of course, the Solaris NFSv4 client won't send >> this user over the wire.) >> Giving "unknown" a userid matters when it comes to the rest of the >> stack. For example, the ACL structures (ace_t and aclent_t) use >> uid_t's to distinguish the users and groups in the ACL. >> Thanks, >> Lisa > > I would expect this to mean that the local uid doesn't matter in > that case, right? Or are we hardcoding the proposed number in > the kernel?
[UID | GID]_UNKNOWN will be defined in usr/src/uts/common/sys/param.h (like what is done for [UID | GID]_NOBODY) and NFS will use this. Thanks, Lisa
