I am running Fedora 9 with the mls policy and was investigating why my setroubleshoot was not working. I found the following in /var/log/messages: Nov 3 09:27:39 localhost kernel: SELinux: inode_doinit_with_dentry: context_to_sid(system_u:object_r:setroubleshoot_var_lib_t:s0) returned 22 for dev=dm-2 ino=23923693 Nov 3 09:27:40 localhost kernel: SELinux: inode_doinit_with_dentry: context_to_sid(system_u:object_r:setroubleshoot_var_log_t:s0) returned 22 for dev=dm-2 ino=23923743 Nov 3 09:27:40 localhost kernel: SELinux: inode_doinit_with_dentry: context_to_sid(system_u:object_r:setroubleshoot_var_run_t:s0) returned 22 for dev=dm-2 ino=23923744 ... Nov 3 18:22:55 localhost setroubleshoot: [program.ERROR] setroubleshoot generated AVC, exiting to avoid recursion, context=system_u:system_r:initrc_t:SystemLow:SystemLow-SystemHigh, AVC scontext=system_u:system_r:initrc_t:s0-s15:c0.c1023 Upon using the Policy Analysis tool I found that none of the setroubleshoot_var_*_t types were associated with the object_r role. Is this an issue with the setroubleshoot policy? Andy -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
