Description of problem: type=AVC msg=audit(1177979939.505:177768): avc: denied { signull } for pid=15541 comm="setroubleshootd" scontext=user_u:system_r:setroubleshootd_t:s0 tcontext=user_u:system_r:setroubleshootd_t:s0 tclass=process type=SYSCALL msg=audit(1177979939.505:177768): arch=40000003 syscall=37 success=yes exit=0 a0=3cb3 a1=0 a2=e1cbb4 a3=b65e50f8 items=0 ppid=1 pid=15541 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) comm="setroubleshootd" exe="/usr/bin/python" subj=user_u:system_r:setroubleshootd_t:s0 key=(null) Version-Release number of selected component (if applicable): selinux-policy-2.6.1-1 selinux-policy-targeted-2.6.1-1 How reproducible: Everytime, just start setroubleshoot. Actual results: AVC denied message, setroubleshoot is exiting... Expected results: No AVC denied message, no quitting setroubleshoot.
type=AVC msg=audit(1178136814.147:178768): avc: denied { signull } for pid=5868 comm="setroubleshootd" scontext=user_u:system_r:setroubleshootd_t:s0 tcontext=user_u:system_r:unconfined_t:s0 tclass=process type=SYSCALL msg=audit(1178136814.147:178768): arch=40000003 syscall=37 success=yes exit=0 a0=361a a1=0 a2=1128bb4 a3=b6400188 items=0 ppid=1 pid=5868 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) comm="setroubleshootd" exe="/usr/bin/python" subj=user_u:system_r:setroublesootd_t:s0 key=(null)
How did you get this to happen?
I'm just starting setroubleshootd and waiting some time until it kills itself.
Fixed in selinux-policy-2.6.3-1.fc7
Is 2.6.3-1 somewhere available during the merge?
type=AVC msg=audit(1178387459.584:180684): avc: denied { signull } for pid=27007 comm="setroubleshootd" scontext=user_u:system_r:setroubleshootd_t:s0 tcontext=user_u:system_r:rpm_t:s0 tclass=process type=SYSCALL msg=audit(1178387459.584:180684): arch=40000003 syscall=37 success=yes exit=0 a0=6895 a1=0 a2=ffebb4 a3=b513cbe0 items=0 ppid=1 pid=27007 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) comm="setroubleshootd" exe="/usr/bin/python" subj=user_u:system_r:setroubleshootd_t:s0 key=(null)"
Daniel, looks like setroubleshootd has problems with signull?!
NO! This bug is not fixed in selinux-policy-targeted-2.6.4-8: type=AVC msg=audit(1180177580.521:188757): avc: denied { signull } for pid=16328 comm="setroubleshootd" scontext=user_u:system_r:setroubleshootd_t:s0 tcontext=user_u:system_r:unconfined_t:s0 tclass=process type=SYSCALL msg=audit(1180177580.521:188757): arch=40000003 syscall=37 success=yes exit=0 a0=4f19 a1=0 a2=10c8c14 a3=b524f008 items=0 ppid=1 pid=16328 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty= (none) comm="setroubleshootd" exe="/usr/bin/python" subj=user_u:system_r:setroubleshootd_t:s0 key=(null) See also comment #6 at this bug report.
Ping?
I'm assuming this bug isn't also fixed in selinux-policy-targeted-2.6.5-2
It should be.
selinux-policy-2.6.4-13 definitely has the fix.
Should be fixed in the current release