Control: tags -1 + moreinfo

Hello Emmanuel Chantreau.

Thanks for your bug report.

On Tue, Aug 04, 2015 at 07:34:45AM +0200, Emmanuel Chantreau wrote:
> Package: libmount1
> Version: 2.27~rc1-1
> Severity: normal
> Tags: upstream
> 
> hi
> 
> The fstab line:
> 
> curlftpfs#emmanuel:password@telemmanuel:2221    /mpnts/telephone-emmanuel
> fuse    noauto,rw,user,uid=1000,_netdev 0       0
> 
> I can mount/umount as root without problem, but for a normal user I can just
> mount:
> 
> emmanuel@fanti: ~
> $ mount /mpnts/telephone-emmanuel
> emmanuel@fanti: ~
> $ ls -d /mpnts/telephone-emmanuel/a*
> /mpnts/telephone-emmanuel/acct/
> emmanuel@fanti: ~
> $ umount /mpnts/telephone-emmanuel
> umount: /mpnts/telephone-emmanuel: Permission denied
> emmanuel@fanti: ~
> $ tail -n1 /etc/mtab
> curlftpfs#ftp://emmanuel:tytotu@telemmanuel:2221/ /mpnts/telephone-emmanuel
> fuse rw,nosuid,nodev,noexec,relatime,user_id=1000,group_id=1000 0 0
> 
> This bug is already known:
> http://fuse.996288.n3.nabble.com/Cannot-umount-as-non-root-user-anymore-
> td689.html
> http://sourceforge.net/p/fuse/mailman/message/29878050/
> 
> As explained, the "user" option is not in mtab and then a normal user can't
> umount.

I'm not sure why you think this is an issue in util-linux at all.
I've from experience learned that whenever someone reports an issue
related to fuse, always assume the problem is on the fuse side.
I guess an external mount helper is used? Or is the fuse things
entirely handled inside the kernel side of fuse?
Please further explain what you think the issue in util-linux is.

Could you please list what /etc/mtab is on your system?
It's supposed to be a symlink to /proc/mounts, eg:
$ ls -l /etc/mtab 
lrwxrwxrwx 1 root root 12 jan 13  2014 /etc/mtab -> /proc/mounts


Since a while util-linux does not use /etc/mtab at all anymore,
to avoid issues where /etc/mtab is an outdated obsolete plain file.

See http://sources.debian.net/src/util-linux/2.26.2-9/debian/rules/#L26


Regards,
Andreas Henriksson


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to