Bug 1297184 - Mounting with "-o noatime" or "-o noexec" causes "nosuid,nodev" to be set as well
Mounting with "-o noatime" or "-o noexec" causes "nosuid,nodev" to be set as ...
Status: CLOSED NEXTRELEASE
Product: GlusterFS
Classification: Community
Component: fuse (Show other bugs)
3.6.8
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: bugs@gluster.org
: Triaged
Depends On: 1297182
Blocks: 1162910
  Show dependency treegraph
 
Reported: 2016-01-10 06:34 EST by Niels de Vos
Modified: 2016-08-23 08:47 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1297182
Environment:
Last Closed: 2016-08-23 08:47:41 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Niels de Vos 2016-01-10 06:34:33 EST
+++ This bug was initially created as a clone of Bug #1297182 +++
+++                                                           +++
+++ Use this bug to backport the fix to release-3.6           +++

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.
Comment 1 Niels de Vos 2016-08-23 08:47:41 EDT
This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. This bug has been fixed in more recent GlusterFS releases. If you still face this bug with the newer GlusterFS versions, please open a new bug.

Note You need to log in before you can comment on or make changes to this bug.