Bug 478892
Summary: | AVC storm brings setroubleshoot deamon down on its own AVC | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jaroslav Franek <jarin.franek> |
Component: | setroubleshoot | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | bloch, dwalsh, jdennis, mgrepl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-12-18 07:30:15 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 517000 |
Description
Jaroslav Franek
2009-01-05 21:16:56 UTC
The problem here is a bad kernel that is causing bogus avc messages one of them on setroubleshoot, setroubleshoot dies when it sees an avc about itself since it does not want to go into an infinite loop. So Logwatch should not generate AVCs. The setroubleshoot daemon should not generate AVC. Are both caused by a bad kernel. The setroubleshoot deamon should handle its own AVC death better (cleanup PID file, not damage its data files) This is a bug. I agree. Just for reference, the rogue kernel is logged under Bug #478299. Different AVCs but I am sure the cause is the same - ext4 (and missing patch in the kernel). As for the setroubleshoot daemon, I guess calling sys.exit(0) on AVC from a context of a worker thread is probably causing the 'damaged files' - another thread got interrupted while writing data. The storm of AVCs might have kept multiple threads occupied. This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |