Bug 1694321

Summary: [abrt] systemd: systemd killed by SIGSEGV
Product: [Fedora] Fedora Reporter: lonelywoolf
Component: libcap-ngAssignee: Steve Grubb <sgrubb>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: lnykryn, msekleta, sgrubb, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a5123f362d319799ae1b2686fe8644d2fe392950
Whiteboard: abrt_hash:f9aca75f7c6ba20cdca0b42da2f7ec112bfcf4ce;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-21 19:33:57 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:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: exploitable none

Description lonelywoolf 2019-03-30 12:39:50 UTC 
Version-Release number of selected component:
systemd-239-12.git8bca462.fc29

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 3
cmdline:        /usr/lib/systemd/systemd --user
executable:     /usr/lib/systemd/systemd
journald_cursor: s=1de52392a41c448f91f92b688a823a97;i=13c77;b=99a7244c55484f9d9f046ad2f0ddbe52;m=3d3cd5d36;t=5854eab924e66;x=d055130f6a237de2
kernel:         5.0.4-200.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ??
 #1 deinit at cap-ng.c:161
 #2 __run_fork_handlers at register-atfork.c:134
 #3 __libc_fork at ../sysdeps/nptl/fork.c:137
 #4 exec_spawn at ../src/core/execute.c:3497
 #5 service_spawn at ../src/core/service.c:1463
 #6 service_enter_start at ../src/core/service.c:1961
 #7 service_enter_start_pre at ../src/core/service.c:2029
 #8 service_start at ../src/core/service.c:2272
 #9 unit_start at ../src/core/unit.c:1850
Comment 1 lonelywoolf 2019-03-30 12:39:54 UTC 
Created attachment 1549779 [details]
File: backtrace
Comment 2 lonelywoolf 2019-03-30 12:39:55 UTC 
Created attachment 1549780 [details]
File: cgroup
Comment 3 lonelywoolf 2019-03-30 12:39:57 UTC 
Created attachment 1549781 [details]
File: core_backtrace
Comment 4 lonelywoolf 2019-03-30 12:39:59 UTC 
Created attachment 1549782 [details]
File: cpuinfo
Comment 5 lonelywoolf 2019-03-30 12:40:04 UTC 
Created attachment 1549783 [details]
File: dso_list
Comment 6 lonelywoolf 2019-03-30 12:40:06 UTC 
Created attachment 1549784 [details]
File: environ
Comment 7 lonelywoolf 2019-03-30 12:40:08 UTC 
Created attachment 1549785 [details]
File: limits
Comment 8 lonelywoolf 2019-03-30 12:40:14 UTC 
Created attachment 1549786 [details]
File: maps
Comment 9 lonelywoolf 2019-03-30 12:40:16 UTC 
Created attachment 1549787 [details]
File: mountinfo
Comment 10 lonelywoolf 2019-03-30 12:40:19 UTC 
Created attachment 1549788 [details]
File: open_fds
Comment 11 lonelywoolf 2019-03-30 12:40:21 UTC 
Created attachment 1549789 [details]
File: proc_pid_status
Comment 12 lonelywoolf 2019-03-30 12:40:23 UTC 
Created attachment 1549790 [details]
File: var_log_messages
Comment 13 lonelywoolf 2019-03-30 12:40:25 UTC 
Created attachment 1549791 [details]
File: exploitable
Comment 14 Zbigniew Jędrzejewski-Szmek 2019-10-21 18:07:01 UTC 
I think this might be related to this patch:
https://github.com/stevegrubb/libcap-ng/commit/7759e6f8469eb33aef1a1d5eba5d300c3a8fcb63

Steve, any idea why it would crashing here?
Comment 15 Steve Grubb 2019-10-21 18:54:02 UTC 
This was found by bug 1680481. That has some more background information. This was subsequently fixed in libcap-ng-0.7.9-7. This appears to be reported about the time that it was found in apache. I'd say this bug report can be closed since the fix was pushed out a long time ago.
Comment 16 Zbigniew Jędrzejewski-Szmek 2019-10-21 19:33:57 UTC 
Many thanks!

*** This bug has been marked as a duplicate of bug 1680481 ***