Bug 1287878 - glusterfs does not allow passing standard SElinux mount options to fuse
glusterfs does not allow passing standard SElinux mount options to fuse
Product: GlusterFS
Classification: Community
Component: scripts (Show other bugs)
x86_64 All
high Severity high
: ---
: ---
Assigned To: Manikandan
: SELinux, Triaged
Depends On: 1287763
Blocks: glusterfs-3.6.7
  Show dependency treegraph
Reported: 2015-12-02 17:10 EST by Niels de Vos
Modified: 2016-09-20 00:29 EDT (History)
4 users (show)

See Also:
Fixed In Version: glusterfs-v3.6.8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1287763
Last Closed: 2016-02-04 03:49:01 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Niels de Vos 2015-12-02 17:10:23 EST
+++ This bug was initially created as a clone of Bug #1287763 +++
+++                                                           +++
+++ Use this bug to provide a backport to release-3.6         +++

Description of problem:

With older versions of gluster, say 3.5.3, glusterfs supports setting selinux context over fuse.glusterfs mountpoint. After 3.6.1, it throws an error : "Invalid option: context". 

The problem is because of a change in mount.glusterfs script. With older versions, it works fine.

Version-Release number of selected component (if applicable):

How reproducible:
Always in versions from 3.6

Steps to Reproduce:

Actual results:
It throws an error "Invalid option: context"

Expected results:
Inform FUSE that the glusterfs sub-filesystem supports SElinux while passing mount options and allow to set selinux context over the mountpoint.

Additional info:

When you set selinux context, the same can be verfied in /proc/mounts:

vm1:sel /qwe1 fuse.glusterfs rw,context=system_u:object_r:user_home_t:s0,relatime,user_id=0,group_id=0,default_    permissions,allow_other,max_read=131072 0 0

--- Additional comment from Vijay Bellur on 2015-12-02 21:56:01 CET ---

REVIEW: http://review.gluster.org/12858 (fuse: pass default SElinux mount options on to the kernel) posted (#1) for review on master by Niels de Vos (ndevos@redhat.com)
Comment 1 Vijay Bellur 2015-12-03 06:14:10 EST
REVIEW: http://review.gluster.org/12871 (fuse: pass default SElinux mount options on to the kernel) posted (#1) for review on release-3.6 by Manikandan Selvaganesh (mselvaga@redhat.com)
Comment 2 Vijay Bellur 2015-12-16 06:27:27 EST
COMMIT: http://review.gluster.org/12871 committed in release-3.6 by Raghavendra Bhat (raghavendra@redhat.com) 
commit b55959c5909b3c32aca18f0c77eced134b38db56
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Dec 2 21:19:56 2015 +0100

    fuse: pass default SElinux mount options on to the kernel
    In order to set default SElinux contexts on a Gluster mount, the
    standard SElinux mount options need to be passed to the kernel. The
    mount(8) manual page lists "context", "fscontext", "defcontext" and
    "rootcontext" as valid options.
            Backport of http://review.gluster.org/#/c/12858/
    Cherry-picked from commit 5e81233f0a3c153e03c437a164ac2ca21314bdec
    > BUG: 1287763
    > Change-Id: I015fe27e4c6ff36a030e3480b23141aca2d91fc2
    > Signed-off-by: Niels de Vos <ndevos@redhat.com>
    > Reviewed-on: http://review.gluster.org/12858
    > Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    > Tested-by: Gluster Build System <jenkins@build.gluster.com>
    > Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    > Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    BUG: 1287878
    Change-Id: I015fe27e4c6ff36a030e3480b23141aca2d91fc2
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/12871
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
Comment 3 Kaushal 2016-02-04 03:49:01 EST
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v3.6.8, please open a new bug report.

glusterfs-v3.6.8 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://www.gluster.org/pipermail/gluster-users/2016-January/025161.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

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