Bug 1378705

Summary: SELinux is preventing gnome-shell from 'getattr' accesses on the file /run/mount/utab.
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: alexus_m, alex.vizor, arturpolak1, balay, bugzilla, c.steinseifer, dominick.grift, dwalsh, fedora, fredoche, grosales, jeremy, lvrabec, mgrepl, mikhail.v.gavrilov, plautrba, scampa.giovanni
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d058202f1d91f1236e89ff2a31b1b4605ac033c20351de3ad533e0f1141fa1b1;VARIANT_ID=workstation;
Fixed In Version: selinux-policy-3.13.1-219.fc25 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-14 19:34:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joachim Frieben 2016-09-23 07:05:17 UTC
Description of problem:
SELinux is preventing gnome-shell from 'getattr' accesses on the file /run/mount/utab.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that gnome-shell should be allowed getattr access on the utab file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell
# semodule -X 300 -i my-gnomeshell.pp

Additional Information:
Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                system_u:object_r:mount_var_run_t:s0
Target Objects                /run/mount/utab [ file ]
Source                        gnome-shell
Source Path                   gnome-shell
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-214.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.8.0-0.rc7.git0.1.fc25.x86_64 #1
                              SMP Mon Sep 19 15:24:06 UTC 2016 x86_64 x86_64
Alert Count                   1
First Seen                    2016-09-23 09:01:22 CEST
Last Seen                     2016-09-23 09:01:22 CEST
Local ID                      20d2b347-0de6-4c63-9aae-3ceb88e6964e

Raw Audit Messages
type=AVC msg=audit(1474614082.866:162): avc:  denied  { getattr } for  pid=983 comm="gnome-shell" path="/run/mount/utab" dev="tmpfs" ino=10665 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:mount_var_run_t:s0 tclass=file permissive=0


Hash: gnome-shell,xdm_t,mount_var_run_t,file,getattr

Version-Release number of selected component:
selinux-policy-3.13.1-214.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.0-0.rc7.git0.1.fc25.x86_64
type:           libreport

Comment 1 Satish Balay 2016-09-23 13:50:02 UTC
Description of problem:
- Upgrade from F24 to F25 alpha
- update to latest F25 (currently upated to latest 'updates-testing')
- reboot
- on login, gnome-shell freezes for 30 sec or so
- On checking selinux troubleshooter - I see this altert.

This freeze issue started with one of the updates [to 'fedora' repo] - from a few days back.. I don't know if that corresponded with the same selinux message or not

Version-Release number of selected component:
selinux-policy-3.13.1-214.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.0-0.rc7.git0.1.fc25.x86_64
type:           libreport

Comment 2 Fedora Admin XMLRPC Client 2016-09-27 15:04:11 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Jeremy Cline 2016-09-29 13:20:49 UTC
Description of problem:
It seemed to happen on boot.

Version-Release number of selected component:
selinux-policy-3.13.1-215.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.0-0.rc8.git0.1.fc25.x86_64+debug
type:           libreport

Comment 4 arturpolak1 2016-10-03 08:21:02 UTC
Description of problem:
sosreport?

Version-Release number of selected component:
selinux-policy-3.13.1-215.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.0-0.rc8.git0.1.fc25.x86_64
type:           libreport

Comment 5 Alexander Mayorov 2016-10-03 10:05:48 UTC
*** Bug 1381166 has been marked as a duplicate of this bug. ***

Comment 6 Giovanni Campagna 2016-10-10 18:03:14 UTC
Description of problem:
I bet this is caused by the new libmount code in glib.

gnome-shell needs to enumerate mounts because it handles automounting, and even though this is gdm's gnome-shell, where automounting is disabled, the volume monitor is probably initialized anyway

Version-Release number of selected component:
selinux-policy-3.13.1-214.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.0-0.rc7.git0.1.fc25.x86_64
type:           libreport

Comment 7 Fedora Update System 2016-10-12 01:53:42 UTC
selinux-policy-3.13.1-219.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-552be55062

Comment 8 Fedora Update System 2016-10-14 19:34:27 UTC
selinux-policy-3.13.1-219.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.