Bug 1523811

Summary: allow syslogd_t container_log_t:dir create;
Product: Red Hat Enterprise Linux 7 Reporter: Qian Cai <qcai>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: high Docs Contact:
Priority: high    
Version: 7.5CC: dwalsh, lmiksik, lvrabec, mgrepl, mmalik, plautrba, ssekidde
Target Milestone: betaKeywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 12:47:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Qian Cai 2017-12-08 19:04:41 UTC
Description of problem:
While running the runc test suite, it generated lots of avc.

time->Fri Dec  8 13:54:36 2017
type=AVC msg=audit(1512759276.886:1162): avc:  denied  { create } for  pid=479 comm="systemd-journal" name="9c728d01022a495994e1f3af881342e8" scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:object_r:container_log_t:s0 tclass=dir

# audit2allow -a


#============= syslogd_t ==============
allow syslogd_t container_log_t:dir create;

Version-Release number of selected component (if applicable):
RHEL-7.5-20171130.0
selinux-policy-3.13.1-180.el7.noarch
docker-latest-1.13.1-36.git9a813fa.el7.ppc64le
container-selinux-2.33-1.git86f33cd.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. setup docker-latest with thin-pool.
2. run runc test suite 
   https://fedorapeople.org/cgit/caiqian/public_git/runctst.git/
3. monitor avc from another terminal # watch ausearch -m avc -ts recent

Comment 1 Daniel Walsh 2017-12-10 11:57:11 UTC
Fixed by
https://github.com/fedora-selinux/selinux-policy/pull/208

Comment 7 errata-xmlrpc 2018-04-10 12:47:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0763