Comment 3 for bug 859259

Revision history for this message
Robert Hutton (rwh-helms-deep) wrote :

Interestingly, I've noticed a difference between using mount.cifs setuid root (invoked as a normal user) and actually running mount.cifs as root, using sudo:

mount.cifs --verbose -o rw,user=<domain>/rwh,uid=1000,gid=1000 //<fileserver>/<share>/<directory> /media/<share>
Password:
mount.cifs kernel mount options: ip=<myip>,unc=\\<fileserver>\<share>,noauto,uid=0,gid=0,ver=1,user=rwh,domain=<domain>,prefixpath=<directory>,pass=********

sudo mount.cifs --verbose -o rw,user=<domain>/rwh,uid=1000,gid=1000 //<fileserver>/<share>/<directory> /media/<share>
Password:
mount.cifs kernel mount options: ip=<myip>,unc=\\<fileserver>\<share>,uid=1000,gid=1000,ver=1,user=rwh,domain=<domain>,prefixpath=<directory>,pass=********

Note the difference between the reported uid and gid values. Perhaps this is a change in the way the kernel module behaves given a setuid root mount.cifs?