Bug 796979

Summary: SELinux is preventing /bin/systemd-tmpfiles from 'setattr' accesses on the None LC_MESSAGES.
Product: [Fedora] Fedora Reporter: Henry Kroll <nospam>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: dominick.grift, dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:386e19b8e4eb45102a90e908adb32d208799bbc28420dbbc6964aeb14e56c1c7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-27 09:41:28 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 Henry Kroll 2012-02-24 00:28:23 UTC
libreport version: 2.0.8
executable:     /usr/bin/python
hashmarkername: setroubleshoot
kernel:         3.2.7-1.fc16.x86_64
reason:         SELinux is preventing /bin/systemd-tmpfiles from 'setattr' accesses on the None LC_MESSAGES.
time:           Thu 23 Feb 2012 05:26:24 PM MST

description:
:SELinux is preventing /bin/systemd-tmpfiles from 'setattr' accesses on the None LC_MESSAGES.
:
:*****  Plugin catchall (100. confidence) suggests  ***************************
:
:If you believe that systemd-tmpfiles should be allowed setattr access on the LC_MESSAGES <Unknown> 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 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                unconfined_u:object_r:user_home_t:s0
:Target Objects                LC_MESSAGES [ None ]
:Source                        systemd-tmpfile
:Source Path                   /bin/systemd-tmpfiles
:Port                          <Unknown>
:Host                          (removed)
:Source RPM Packages           systemd-units-37-13.fc16.x86_64
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-75.fc16.noarch selinux-
:                              policy-3.10.0-71.fc16.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.2.7-1.fc16.x86_64 #1 SMP Tue
:                              Feb 21 01:40:47 UTC 2012 x86_64 x86_64
:Alert Count                   41
:First Seen                    Thu 23 Feb 2012 01:27:05 PM MST
:Last Seen                     Thu 23 Feb 2012 03:53:45 PM MST
:Local ID                      90b4c471-b5de-4409-8fca-919601eafa3c
:
:Raw Audit Messages
:type=AVC msg=audit(1330037625.107:160): avc:  denied  { setattr } for  pid=1687 comm="systemd-tmpfile" name="LC_MESSAGES" dev=dm-1 ino=1054809 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=dirnode=(removed) type=SYSCALL msg=audit(1330037625.107:160): arch=c000003e syscall=280 success=no exit=-13 a0=a a1=0 a2=7fff46f6bfc0 a3=0 items=0 ppid=1 pid=1687 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-tmpfile" exe="/bin/systemd-tmpfiles" subj=system_u:system_r:systemd_tmpfiles_t:s0 key=(null)
:
:
:Hash: systemd-tmpfile,systemd_tmpfiles_t,user_home_t,None,setattr
:
:audit2allow
:
:
:audit2allow -R
:
:

Comment 1 Daniel Walsh 2012-02-24 19:12:58 UTC
Did you mv some files out of ~ into /tmp?

ls -lZ /tmp

Look for user_home_t and remove them.

Comment 2 Henry Kroll 2012-02-25 00:47:06 UTC
Must be gone now since find /tmp -context '*home*' returns nothing. I can't remember what I was doing, but I kept getting lots of those errors. It's python, so I think it was a yum update with weeks of uptime. I have since rebooted and did another update of two video driver modules, did some more playing around with python printing in various locales and no errors so fine, I guess.

Comment 3 Miroslav Grepl 2012-02-27 09:41:28 UTC
Ok, could you reopen the bug if this happens again. Thank you.