[Bugs] [Bug 1297183] New: Mounting with "-o noatime" or "-o noexec" causes "nosuid, nodev" to be set as well
bugzilla at redhat.com
bugzilla at redhat.com
Sun Jan 10 11:32:05 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1297183
Bug ID: 1297183
Summary: Mounting with "-o noatime" or "-o noexec" causes
"nosuid,nodev" to be set as well
Product: GlusterFS
Version: 3.7.7
Component: fuse
Keywords: Triaged
Assignee: bugs at gluster.org
Reporter: ndevos at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com,
rabhat at redhat.com, rgowdapp at redhat.com
Depends On: 1294811, 1297182
+++ This bug was initially created as a clone of Bug #1297182 +++
+++ +++
+++ Use this bug for backporting the change to release-3.7 +++
Description of problem:
With additional tests after fixing bug 1296992 I noticed that mounting with "-o
noatime" or "-o noexec" the additional "nosuid,nodev" mount options are set as
well.
Mounting without any options does not add "nosuid,nodev"
Version-Release number of selected component (if applicable):
mainline and branches with backport of bug 1296992
How reproducible:
100%
Steps to Reproduce:
1. mount a Gluster volume with "-o noatime" or "-o noexec"
2. compare mount options in /proc/mounts
Actual results:
The "nosuid,nodev" mount options are automatically added, even when not
specified in the mount command.
Expected results:
Mounting with additional options should only add/change those options, not
automatically add others.
Additional info:
This most likely is caused by the flag handling in do_mount() in
contrib/fuse-util/fusermount.c. Needs some investigation on the reasoning
behind this.
--- Additional comment from Niels de Vos on 2016-01-10 12:29:38 CET ---
Oop, bug 1294809 is the one that makes it possible again to mount with "-o
noatime" and the like.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1294811
[Bug 1294811] mount options no longer valid: noexec, nosuid, noatime
https://bugzilla.redhat.com/show_bug.cgi?id=1297182
[Bug 1297182] Mounting with "-o noatime" or "-o noexec" causes
"nosuid,nodev" to be set as well
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list