RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1478285 - probe_systemdunitdependency failed with segmentation fault
Summary: probe_systemdunitdependency failed with segmentation fault
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openscap
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Jan Černý
QA Contact: Matus Marhefka
Jan Fiala
URL:
Whiteboard:
Depends On:
Blocks: 1477664 1793050
TreeView+ depends on / blocked
 
Reported: 2017-08-04 08:14 UTC by Hao Chang Yu
Modified: 2023-12-15 15:57 UTC (History)
11 users (show)

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.
Clone Of:
: 1793050 (view as bug list)
Environment:
Last Closed: 2020-09-29 19:53:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3914 0 None None None 2020-09-29 19:53:43 UTC

Comment 5 Jan Černý 2018-01-19 16:47:14 UTC 
I think that the segfault happens in the DBus library. It is possible that we use the library wrong, but it is also possible there is a bug in the DBus library itself.
Comment 10 Matus Marhefka 2018-11-14 14:28:38 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.
Comment 11 Renaud Métrich 2019-05-18 13:15:09 UTC 
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< --------
Comment 15 Jan Černý 2020-01-27 12:59:03 UTC 
A fix has been proposed to upstream in https://github.com/OpenSCAP/openscap/pull/1474
Comment 16 Jan Černý 2020-02-10 08:56:53 UTC 
This bug has been fixed in upstream in https://github.com/OpenSCAP/openscap/pull/1474.
Comment 26 errata-xmlrpc 2020-09-29 19:53:30 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.