Re: UID/GID override on CIFS mounts to Samba and proposed new mount parameter to disable Unix Extensions on the client

["Steve French" <smfrench@gmail.com>]

The CIFS Unix Extensions are used by multiple clients now (not just
Linux) but originally I thought that it might be confusing to Linux
users  to call the configuration setting for that in /proc/fs/cifs
"Unix" instead of "Linux" (and since it has been there for years and
is externally visible, it is probably not a good idea to change its
name in proc) but for a mount option it might make sense to refer to
them as "unixextensions=no" (similar to Samba server's smb.conf
setting name).  I also though about calling it:

"noposix" or "noposixpaths" ("posix paths" are one of the capabilities
negotiated when Unix Extension are turned on) but that might imply
that the client is turning off compensations that is can use for
mounting to Windows (like JRA's byte range lock emulation, and the
optional SFU-like emulation of device files and symlinks)

On 4/30/07, Anton Altaparmakov <aia21@cam.ac.uk> wrote:
> On 30 Apr 2007, at 15:26, Steve French wrote:
> > When CIFS Unix Extensions are negotiated we get the Unix uid and gid
> > owners of the file from the server (on the Unix Query Path Info
> > levels), but if the server's uids don't match the client uid's users
> > were having to disable the Unix Extensions (which turned off features
> > they still wanted).   The attached patch allows users to override uid
> > and/or gid for file/directory owner with a default uid and/or gid
> > specified at mount (as is often done when mounting from Linux cifs
> > client to Windows server).  The attached patch also displays the uid
> > and gid used by default in /proc/mounts (if applicable).
> >
> > I also would like suggestions on what we should call a proposed mount
> > option (not coded yet) which would disable the CIFS Unix Extensions on
> > a per-mount basis (or more likely actually would require it on the
> > first mount to the server, subsequent mounts would probably inherit
> > the capabilities).  Current cifs code can disable mount options before
> > a mount by specifying
> >
> >     "echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled")
> >
> > but it might be easier to specify it on mount (e.g.
> > "nolinuxextensions" or "linuxextensions=no" ?).    Slightly harder
> > would be disabling Unix Extensions after the user has already mounted
> > (with Unix Extensions) to the same server (perhaps to a different
> > share).  How important would it be to have two mounts to the same
> > server one with unix extensions and one without?
>
> Why "linuxextensions"?  I thought those are the "UNIX extensions"
> that Samba provides no matter on which platform it is run such as
> Linux, Mac OS X, Solaris, etc...
>
> Best regards,
>
>         Anton


--
Thanks,

Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/