Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1076232

Summary: systemd[1]: segfault at a8 ip 00007f431b2fdc7e sp 00007fff6adcbef0 error 4 in systemd[7f431b26a000+10a000]
Product: Red Hat Enterprise Linux 7 Reporter: Jaroslav Kortus <jkortus>
Component: systemdAssignee: systemd-maint
Status: CLOSED CURRENTRELEASE QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: high    
Version: 7.0CC: jkortus, jpayne, lnykryn, systemd-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 12:11:56 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:
Attachments:
Description Flags
core file none

Description Jaroslav Kortus 2014-03-13 20:34:03 UTC
Description of problem:
systemd crashed

Happend on one of your invocations of qarsh (kind of inetd service spawning daemon on remote connection)

Version-Release number of selected component (if applicable):
systemd-208-8.el7.x86_64

How reproducible:
unknown

Steps to Reproduce:
1. 
2.
3.

Actual results:
crash

Expected results:
no crash

Additional info:
Core was generated by `/usr/lib/systemd/systemd --switched-root --system --deserialize 23'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f431973f00b in raise (sig=sig@entry=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
37	  return INLINE_SYSCALL (tgkill, 3, pid, THREAD_GETMEM (THREAD_SELF, tid),
(gdb) bt
#0  0x00007f431973f00b in raise (sig=sig@entry=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
#1  0x00007f431b28a74e in crash (sig=11) at src/core/main.c:148
#2  <signal handler called>
#3  0x00007f431b2fdc7e in unit_unwatch_pid (u=u@entry=0x7f431c3fffe0, pid=16297) at src/core/unit.c:1688
#4  0x00007f431b28c2a6 in manager_dispatch_sigchld (m=m@entry=0x7f431c1c59e0) at src/core/manager.c:1392
#5  0x00007f431b291aed in manager_process_signal_fd (m=<optimized out>) at src/core/manager.c:1636
#6  process_event (ev=0x7fff6adcc100, m=0x7f431c1c59e0) at src/core/manager.c:1661
#7  manager_loop (m=0x7f431c1c59e0) at src/core/manager.c:1858
#8  0x00007f431b288619 in main (argc=5, argv=0x7fff6adcca68) at src/core/main.c:1667

Comment 1 Jaroslav Kortus 2014-03-13 20:36:11 UTC
Created attachment 874153 [details]
core file

Comment 3 Lukáš Nykrýn 2014-03-14 12:59:59 UTC
208-9 should fix everything that went wrong in 208-8.
https://brewweb.devel.redhat.com/taskinfo?taskID=7203233
Can you please try it?

Comment 4 Jaroslav Kortus 2014-03-14 16:24:57 UTC
so was this a known bug or how should I read it? Given the uncertain reproducibility is hard to tell if it is in newer builds or not.

Comment 5 Lukáš Nykrýn 2014-03-14 16:38:38 UTC
To 208-8 we backport a huge patch from upstream version, but unfortunately there were some parts missing and also there were some bugs even in the upstream.

Comment 7 Justin Payne 2014-03-17 16:44:01 UTC
I have not encountered this since updating to 208-9 from comment #3.

Comment 8 RHEL Program Management 2014-03-25 05:48:06 UTC
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.

Comment 9 Lukáš Nykrýn 2014-06-13 12:11:56 UTC
This is fixed in current version of systemd.