Bug 961304 - SELinux is preventing systemd-tmpfile from 'read' accesses on the lnk_file /var/lock.
SELinux is preventing systemd-tmpfile from 'read' accesses on the lnk_file /v...
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Miroslav Grepl
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-05-09 07:29 EDT by Antonio A. Olivares
Modified: 2013-05-09 07:47 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-05-09 07:47:45 EDT
Type: ---
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 Antonio A. Olivares 2013-05-09 07:29:43 EDT
Description of problem:
SELinux is preventing systemd-tmpfile from 'read' accesses on the lnk_file /var/lock.

*****  Plugin restorecon (94.8 confidence) suggests  *************************

If you want to fix the label. 
/var/lock default label should be var_lock_t.
Then you can run restorecon.
# /sbin/restorecon -v /var/lock

*****  Plugin catchall_labels (5.21 confidence) suggests  ********************

If you want to allow systemd-tmpfile to have read access on the lock lnk_file
Then you need to change the label on /var/lock
# semanage fcontext -a -t FILE_TYPE '/var/lock'
where FILE_TYPE is one of the following: apcupsd_lock_t, apmd_lock_t, automount_lock_t, bin_t, bluetooth_lock_t, boot_t, cert_t, condor_var_lock_t, cupsd_lock_t, denyhosts_var_lock_t, device_t, devlog_t, dirsrv_var_lock_t, dirsrvadmin_lock_t, drbd_lock_t, etc_runtime_t, etc_t, fenced_lock_t, ftpd_lock_t, getty_lock_t, home_root_t, httpd_lock_t, ipsec_mgmt_lock_t, iscsi_lock_t, krb5kdc_lock_t, ld_so_t, lib_t, likewise_pstore_lock_t, local_login_lock_t, locale_t, lockdev_lock_t, logrotate_lock_t, logwatch_lock_t, lvm_lock_t, mailman_lock_t, man_t, mandb_lock_t, mrtg_lock_t, net_conf_t, pkcsslotd_lock_t, pki_ra_lock_t, pki_tomcat_lock_t, pki_tps_lock_t, postgresql_lock_t, pppd_lock_t, proc_t, rhsmcertd_lock_t, ricci_modstorage_lock_t, root_t, rpm_script_tmp_t, rpm_var_cache_t, rpm_var_lib_t, security_t, selinux_config_t, semanage_read_lock_t, semanage_trans_lock_t, shell_exec_t, shorewall_lock_t, slapd_lock_t, src_t, sssd_var_lib_t, sysfs_t, system_cronjob_lock_t, textrel_shlib_t, tmp_t, usr_t, uucpd_lock_t, var_auth_t, var_lock_t, var_run_t, virt_lock_t, xdm_lock_t. 
Then execute: 
restorecon -v '/var/lock'

*****  Plugin catchall (1.44 confidence) suggests  ***************************

If you believe that systemd-tmpfile should be allowed read access on the lock lnk_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# grep systemd-tmpfile /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:systemd_tmpfiles_t:s0
Target Context                system_u:object_r:var_t:s0
Target Objects                /var/lock [ lnk_file ]
Source                        systemd-tmpfile
Source Path                   systemd-tmpfile
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           filesystem-3.1-2.fc18.x86_64
Policy RPM                    selinux-policy-3.11.1-92.fc18.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.8.11-200.fc18.x86_64 #1 SMP Wed
                              May 1 19:44:27 UTC 2013 x86_64 x86_64
Alert Count                   1
First Seen                    2013-05-09 06:28:23 CDT
Last Seen                     2013-05-09 06:28:23 CDT
Local ID                      70cbcddb-eee0-4481-884f-c17b1b7e3757

Raw Audit Messages
type=AVC msg=audit(1368098903.455:5): avc:  denied  { read } for  pid=471 comm="systemd-tmpfile" name="lock" dev="sda5" ino=655418 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=lnk_file

Hash: systemd-tmpfile,systemd_tmpfiles_t,var_t,lnk_file,read


#============= systemd_tmpfiles_t ==============
allow systemd_tmpfiles_t var_t:lnk_file read;

audit2allow -R
require {
	type systemd_tmpfiles_t;

#============= systemd_tmpfiles_t ==============

Additional info:
hashmarkername: setroubleshoot
kernel:         3.8.11-200.fc18.x86_64
type:           libreport

Potential duplicate: bug 710743
Comment 1 Miroslav Grepl 2013-05-09 07:47:45 EDT
Could you execute

# restorecon -R -v /var

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