Bug 31491 - permissions on /dev/fuse get broken and fusermount fails
Summary: permissions on /dev/fuse get broken and fusermount fails
Status: CLOSED NOTABUG
Alias: None
Product: Simply Linux
Classification: Distributions
Component: bugs (show other bugs)
Version: 7.0.3
Hardware: all Linux
: P3 major
Assignee: Mikhail Efremov
QA Contact: Andrey Cherepanov
URL:
Keywords:
Depends on: 31490
Blocks:
  Show dependency tree
 
Reported: 2015-11-14 15:04 MSK by Ivan Zakharyaschev
Modified: 2017-06-20 20:26 MSK (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Zakharyaschev 2015-11-14 15:04:31 MSK
+++ This bug was initially created as a clone of Bug #31490 +++

fuse-2.9.2-alt2

I'm using it with "control fusermount public". After some time, the permissions on /dev/fuse lack any permissions for other (i.e., are 0660), and fusermount fails to work.

fuse-2.9.4-alt3 from Sisyphus seems not have this problem.

I've reproduced this in a clean installation of Simply Linux 7.0.5.

Preparation:

install Simply Linux 7.0.5 (x86_64)

service sshd start

install fuse-sshfs 

control fusermount public

The test (as a user):

mkdir test
touch test/a
mkdir mnt
sshfs 0:test mnt
ls mnt
fusermount -u mnt

The first time the test works, because initally the permissions on /dev/fuse are like this:

crw-rw-rw- 1 root fuse 10, 229 ноя 13 17:03 /dev/fuse

but the second time the test fails, because after the first test /dev/fuse lacks the permissions for other.

"control fusermount public" has nothing to do with this (/dev/fuse), it controls the permission needed by fusermount to do a mount.
Comment 1 Ivan Zakharyaschev 2015-11-14 15:09:15 MSK
The permissions on /dev/fuse change after the execution of:

sshfs 0:test mnt

during the first test.
Comment 2 Mikhail Efremov 2017-06-20 20:26:32 MSK
SL-8 hasn't fuse-sshfs. Please open bug for fuse-sshfs if error still exist.