Bug 737443
Summary: | SELinux is preventing dmesg from reading a file in /var/spool/abrt/pyhook-*/*/sos_commands/networking/brctl_show | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Milos Malik <mmalik> |
Component: | abrt | Assignee: | abrt <abrt-devel-list> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | qe-baseos-tools-bugs |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2 | CC: | agk, bmr, dwalsh, gavin, jmoskovc, mnowak, nobody+abrt-devel-list, npajkovs, prc |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-06 14:26:36 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: |
Description
Milos Malik
2011-09-12 06:47:52 UTC
It looks like ABRT is leaking. sosreport is leaking abrt executes: nice sosreport --tmp-dir "$DUMP_DIR" --batch \ --only=anaconda --only=bootloader --only=devicemapper \ --only=filesys --only=hardware --only=kernel --only=libraries \ --only=memory --only=networking --only=nfsserver --only=pam \ --only=process --only=rpm -k rpm.rpmva=off --only=ssh \ --only=startup --only=yum --only=general --only=x11 \ where --tmp-dir points to /var/spool/abrt/ Can we please get some steps to reproduce so we can investigate it? I don't see this with the default set of ABRT tests. Were there any python exceptions recorded during the sos run that triggered this AVC? The only way I can see sos leaking an fd to sos_commands/networking/brctl_show is if there's an unhandled exception while reading from this file. I also don't understand why dmesg is attempting to access this file. Anyway, this has never been seen on "normal" sos runs outside abrtd (and probably can't happen as they normally run unconfined in a root session) so I think abrt needs to look at how it's running the command to avoid it. Can't find a reliable reproducer so I think it's not so critical - moving to 6.4. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. |