Description of problem: In /var/log/messages (variations?) of the attachment show up each few seconds. SELINUX=ENFORCING SELINUXTYPE=targeted Version-Release number of selected component (if applicable): setroubleshoot-2.2.16-1.fc12.x86_64 selinux-policy-3.6.22-2.fc12.noarch selinux-policy-targeted-3.6.22-2.fc12.noarch kernel-2.6.31-0.86.rc3.git5.fc12.x86_64 How reproducible: No idea, just booted after updating (for 20090722 and 20090723). Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 354959 [details] One (humongous) line out of /var/log/messages
John, do you have any idea on this?
Sorry, not at the moment, unfortunately looks like the stack trace was truncated in /var/log/messages, but it should be in /var/log/setroubleshoot/setroubleshoot.log
Created attachment 355555 [details] Requested setroubleshootd.log As of today (rawhide up to date), setroubleshoot-2.2.16-1.fc12.x86_64
Hmm... this looks like the infinite recursion we fixed a while ago in the prune database code where marking an alert caused prune to be called again. Note, that's not the actual error reported, I'm not sure I can explain that error at the moment, but given the depth of the recursion stack I would not be totally surprised if the actual error reported wasn't the consequence of running out of a resource. My suggestion would be to fix the infinite recursion and then see if the other error goes away.
John, do you remember how we prevented the recursion. I am coding prune to set a "prune" flag to true and then having delete_signature, mark_modified, save have a default flag falue true. Finally save calls if not prune: self.prune()
Created attachment 355677 [details] Here is the patch
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fixed in setroubleshoot-2.2.52-1.fc12