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 1545676 - systemd segfaults running test case https://github.com/systemd/systemd-fedora-ci/tree/master/issue-1981
Summary: systemd segfaults running test case https://github.com/systemd/systemd-fedora...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.5
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks: 1549119 1709191 1711872
TreeView+ depends on / blocked
 
Reported: 2018-02-15 13:27 UTC by Susant Sahani
Modified: 2019-05-20 10:29 UTC (History)
5 users (show)

Fixed In Version: systemd-219-56.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1549119 1709191 1711872 (view as bug list)
Environment:
Last Closed: 2018-04-10 11:25:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0711 0 None None None 2018-04-10 11:26:25 UTC

Description Susant Sahani 2018-02-15 13:27:35 UTC
Description of problem:
systemd segfaults running test case https://github.com/systemd/systemd-fedora-ci/tree/master/issue-1981

Version-Release number of selected component (if applicable):
219

How reproducible:

frequesnt
Steps to Reproduce:
Run the test case.


Actual results:
pid1 crashes
Message from syslogd@host-172-16-36-41 at Feb 15 08:24:30 ...
 kernel:systemd[1]: segfault at 1d0 ip 0000563b335fd29c sp 00007ffe8cfdbf90 error 4 in systemd[563b335af000+15f000]

Broadcast message from systemd-journald.eng.rdu2.redhat.com (Thu 2018-02-15 08:24:30 EST):

systemd[1]: Caught <SEGV>, dumped core as pid 7293.


Broadcast message from systemd-journald.eng.rdu2.redhat.com (Thu 2018-02-15 08:24:30 EST):

systemd[1]: Freezing execution.


Message from syslogd@host-172-16-36-41 at Feb 15 08:24:30 ...
 systemd:Caught <SEGV>, dumped core as pid 7293.

Message from syslogd@host-172-16-36-41 at Feb 15 08:24:30 ...
 systemd:Freezing execution.



Expected results:

pid1 should not crash
Additional info:

Comment 3 Jan Synacek 2018-02-16 09:09:19 UTC
https://github.com/lnykryn/systemd-rhel/pull/197

Comment 6 Lukáš Nykrýn 2018-02-19 15:20:11 UTC
fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/197 -> post

Comment 11 errata-xmlrpc 2018-04-10 11:25:34 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, 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-2018:0711


Note You need to log in before you can comment on or make changes to this bug.