Description of problem: Version-Release number of selected component (if applicable): selinux-policy-2.4.6-302.el5 selinux-policy-targeted-2.4.6-302.el5 How reproducible: * not sure, but seen on 2 machines Steps to Reproduce: * run /CoreOS/selinux-policy/Regression/bz271561-corosync-and-similar test on i386/x86_64 machine with RHEL5.7-Server-20110513.0_nfs build Actual results: ---- time->Tue May 17 16:45:19 2011 type=SYSCALL msg=audit(1305665119.991:34): arch=40000003 syscall=37 success=no exit=-13 a0=1 a1=f a2=bff1395a a3=bff13858 items=0 ppid=1 pid=27043 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="ccsd" exe="/sbin/ccsd" subj=root:system_r:ccs_t:s0 key=(null) type=AVC msg=audit(1305665119.991:34): avc: denied { signal } for pid=27043 comm="ccsd" scontext=root:system_r:ccs_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=process ---- Expected results: no AVCs
Is ccs actually sending a signal to process init running with PID 1?
It seems so. type=SYSCALL ... ppid=1 ...
Miroslav add this to both RHEL5 and RHEL6. init_signal(ccs_t)
Fixed in selinux-policy-2.4.6-309.el5
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1069.html