However, mount.cifs ignores the options passed to it by the util-linux
mount when it is not invoked by root. In that case, mount.cifs obtains
the options from the fstab file and does not do any processing to ignore
comments. So the status of this bug should not be invalid, unless
mount.cifs is not
After further investigation, it turns out that mount is actually
handling the options correctly and passing the options (with x-* options
removed) to mount.cifs. The problem is that mount.cifs ignores those
passed options if the user running the mount command is not root, and
just grabs the
output from "mount -v /mnt/mybook":
mount.cifs kernel mount options:
ip=192.168.1.3,unc=\\192.168.1.3\Public,noauto,x-
test.opt,noperm,soft,cache=none,sec=none,uid=1000,gid=1000,user=,pass=
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
--
Public bug reported:
According to the mount(8) man page:
All options prefixed with "x-" are interpreted as comments or as
userspace application-specific options. These options are not stored
in the mtab file, nor sent to the mount.type helpers nor to the
mount(2) system call. The
4 matches
Mail list logo
