Bug 1478285
| Summary: | probe_systemdunitdependency failed with segmentation fault | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Hao Chang Yu <hyu> | |
| Component: | openscap | Assignee: | Jan Černý <jcerny> | |
| Status: | CLOSED ERRATA | QA Contact: | Matus Marhefka <mmarhefk> | |
| Severity: | medium | Docs Contact: | Jan Fiala <jafiala> | |
| Priority: | high | |||
| Version: | 7.6 | CC: | cshabazi, cww, ekolesni, jafiala, jcerny, matyc, mhaicman, mmarhefk, openscap-maint, rmetrich, wpinheir | |
| Target Milestone: | rc | Keywords: | Reopened | |
| Target Release: | --- | Flags: | lcervako:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openscap-1.2.17-10.el7 | Doc Type: | Bug Fix | |
| Doc Text: |
.Recursive dependencies no longer cause OpenSCAP crashes
Because `systemd` units can have dependent units, OpenSCAP scans could encounter cyclical dependencies that caused the scan to terminate unexpectedly. With this update, OpenSCAP no longer analyses previously analysed units. As a result, scans now complete with a valid result even if dependencies are cyclical.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1793050 (view as bug list) | Environment: | ||
| Last Closed: | 2020-09-29 19:53:30 UTC | Type: | Bug | |
| 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: | 1477664, 1793050 | |||
|
Comment 5
Jan Černý
2018-01-19 16:47:14 UTC
Requested information was not provided and we were not able to fully reproduce this bug, therefore closing. Please feel free to reopen if the issue still occurs and if there is a working reproducer available. Hello, I'm reopening this BZ due to being able to reproduce using the reproducer below: 1. Create a broken target trying to run after multi-user.target, but still wanting multi-user.target -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- # cat /etc/systemd/system/broken.target [Unit] Description=Broken target killing oscap's /usr/libexec/openscap/probe_systemdunitdependency After=multi-user.target Wants=multi-user.target [Install] WantedBy=multi-user.target -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 2. Reload systemd and enable the target -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- # systemctl daemon-reload # systemctl enable broken.target -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 3. Execute oscap -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- # oscap xccdf eval --fetch-remote-resources --profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa --rule xccdf_org.ssgproject.content_rule_service_firewalld_enabled /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml Downloading: https://www.redhat.com/security/data/oval/com.redhat.rhsa-RHEL7.xml.bz2 ... ok Title Verify firewalld Enabled Rule xccdf_org.ssgproject.content_rule_service_firewalld_enabled Ident CCE-27361-5 --> sits there -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Result: dbus is heavily used, systemd also, /usr/libexec/openscap/probe_systemdunitdependency consumes more and more memory and later dies with segfault (due to stack overflow) "top" output: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2800 dbus 20 0 68480 2604 1888 S 50.0 0.3 2:27.72 dbus-daemon 1 root 20 0 54408 6720 4204 S 37.0 0.7 1:52.14 systemd 3447 root 20 0 581228 312784 3616 S 12.3 30.8 0:33.44 probe_systemdun -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- A fix has been proposed to upstream in https://github.com/OpenSCAP/openscap/pull/1474 This bug has been fixed in upstream in https://github.com/OpenSCAP/openscap/pull/1474. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (openscap bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:3914 |