Bug 679215

Summary: SELinux is preventing /usr/libexec/gvfs-gdu-volume-monitor from 'getattr' accesses on the file /media/ymis/.hal-mtab-lock.
Product: [Fedora] Fedora Reporter: Flóki Pálsson <flokip>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:3b65970012c20a058b256c68bdfdadec649099bcf1522311a40822b8fb3b1644
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-21 22:30:04 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 Flóki Pálsson 2011-02-21 22:21:20 UTC
SELinux is preventing /usr/libexec/gvfs-gdu-volume-monitor from 'getattr' accesses on the file /media/ymis/.hal-mtab-lock.

*****  Plugin file (36.8 confidence) suggests  *******************************

If you think this is caused by a badly mislabeled machine.
Then you need to fully relabel.
Do
touch /.autorelabel; reboot

*****  Plugin file (36.8 confidence) suggests  *******************************

If you think this is caused by a badly mislabeled machine.
Then you need to fully relabel.
Do
touch /.autorelabel; reboot

*****  Plugin catchall_labels (23.2 confidence) suggests  ********************

If you want to allow gvfs-gdu-volume-monitor to have getattr access on the .hal-mtab-lock file
Then you need to change the label on /media/ymis/.hal-mtab-lock
Do
# semanage fcontext -a -t FILE_TYPE '/media/ymis/.hal-mtab-lock'
where FILE_TYPE is one of the following: system_dbusd_var_lib_t, abrt_helper_exec_t, cgroup_t, policykit_auth_exec_t, selinux_config_t, bin_t, cert_t, user_tmp_t, lib_t, ld_so_t, usr_t, var_t, wtmp_t, xserver_exec_t, default_context_t, pam_console_exec_t, textrel_shlib_t, sssd_public_t, device_t, hwdata_t, locale_t, var_auth_t, dbusd_exec_t, etc_t, fonts_t, user_fonts_t, user_tmpfs_t, logfile, proc_t, rpm_script_tmp_t, sysfs_t, xdm_t, loadkeys_exec_t, xdm_dbusd_t, xdm_spool_t, krb5_keytab_t, fonts_cache_t, user_home_t, ssh_agent_exec_t, plymouthd_var_log_t, system_cronjob_var_lib_t, crack_db_t, ssh_home_t, policykit_var_lib_t, krb5_conf_t, user_tmp_t, xserver_tmpfs_t, sosreport_tmp_t, iceauth_home_t, plymouth_exec_t, xauth_exec_t, xauth_home_t, alsa_etc_rw_t, auth_cache_t, sysctl_dev_t, sysctl_net_t, xdm_tmpfs_t, rpm_tmp_t, rpm_exec_t, security_t, udev_tbl_t, pulseaudio_exec_t, gconf_etc_t, mount_exec_t, shell_exec_t, consolekit_log_t, ld_so_cache_t, pam_exec_t, krb5_home_t, proc_afs_t, var_lib_t, oddjob_mkhomedir_exec_t, xserver_log_t, updpwd_exec_t, dbusd_etc_t, user_home_t, xdm_tmp_t, xserver_t, configfile, domain, userdomain, fusermount_exec_t, rpm_var_cache_t, faillog_t, lastlog_t, proc_net_t, var_log_t, chkpwd_exec_t, policykit_reload_t, xdm_etc_t, xdm_log_t, gnome_home_type, hostname_exec_t, samba_var_t, initrc_var_run_t, abrt_var_run_t, gkeyringd_exec_t, user_cron_spool_t, pam_var_run_t, rpm_var_lib_t, xdm_var_lib_t, xdm_var_run_t, net_conf_t, admin_home_t, init_exec_t, anon_inodefs_t, gconf_home_t, etc_runtime_t, sysctl_kernel_t, sysctl_crypto_t, openct_var_run_t, pcscd_var_run_t, alsa_exec_t, xkb_var_lib_t, consoletype_exec_t, shutdown_exec_t, xdm_rw_etc_t, accountsd_var_lib_t, abrt_t, lib_t, logfile, xdm_exec_t, xdm_home_t, xdm_lock_t, pam_var_console_t, xsession_exec_t, shell_exec_t, krb5_host_rcache_t, cert_t, security_t, net_conf_t, file_context_t. 
Then execute: 
restorecon -v '/media/ymis/.hal-mtab-lock'


*****  Plugin catchall (5.04 confidence) suggests  ***************************

If you believe that gvfs-gdu-volume-monitor should be allowed getattr access on the .hal-mtab-lock 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:
# grep gvfs-gdu-volume /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                system_u:object_r:file_t:s0
Target Objects                /media/ymis/.hal-mtab-lock [ file ]
Source                        gvfs-gdu-volume
Source Path                   /usr/libexec/gvfs-gdu-volume-monitor
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           gvfs-1.7.2-2.fc15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.14-2.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.38-0.rc4.git7.1.fc15.x86_64 #1
                              SMP Mon Feb 14 01:29:48 UTC 2011 x86_64 x86_64
Alert Count                   11
First Seen                    mið 16.feb 2011, 23:07:36 GMT
Last Seen                     mið 16.feb 2011, 23:27:00 GMT
Local ID                      c5cff195-38a0-4e64-8032-70d50e0556bf

Raw Audit Messages
type=AVC msg=audit(1297898820.21:674): avc:  denied  { getattr } for  pid=3119 comm="gvfs-gdu-volume" path="/media/ymis/.hal-mtab-lock" dev=sda2 ino=12 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:file_t:s0 tclass=file


type=SYSCALL msg=audit(1297898820.21:674): arch=x86_64 syscall=lstat success=no exit=EACCES a0=7f6cac005000 a1=7f6cbc3f8b40 a2=7f6cbc3f8b40 a3=100006 items=0 ppid=1 pid=3119 auid=4294967295 uid=42 gid=42 euid=42 suid=42 fsuid=42 egid=42 sgid=42 fsgid=42 tty=(none) ses=4294967295 comm=gvfs-gdu-volume exe=/usr/libexec/gvfs-gdu-volume-monitor subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null)

Hash: gvfs-gdu-volume,xdm_t,file_t,file,getattr

audit2allow

#============= xdm_t ==============
allow xdm_t file_t:file getattr;

audit2allow -R

#============= xdm_t ==============
allow xdm_t file_t:file getattr;

Comment 1 Daniel Walsh 2011-02-21 22:30:04 UTC

*** This bug has been marked as a duplicate of bug 679213 ***