Bug 1046172

Summary: [abrt] p11-kit-trust: dlmmap_locked(): trust killed by SIGBUS
Product: [Fedora] Fedora Reporter: mdmpsyd <mdmpsyd>
Component: p11-kitAssignee: Stef Walter <stefw>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: green, kengert, mclasen, mdmpsyd, stefw, tmraz
Target Milestone: ---Flags: stefw: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/73e6248a78b4bc6c9899f71250c09f2089de1f78
Whiteboard: abrt_hash:166efe2534467f9b7a25be8f0824df252e4e8052
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-07 06:53:17 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: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description mdmpsyd@gmail.com 2013-12-23 23:28:39 UTC 
Version-Release number of selected component:
p11-kit-trust-0.20.1-1.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/bin/trust extract --format=openssl-bundle --filter=certificates --overwrite /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt
crash_function: dlmmap_locked
executable:     /usr/bin/trust
kernel:         3.12.5-302.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 dlmmap_locked at ../src/closures.c:460
 #1 dlmmap at ../src/closures.c:506
 #2 sys_alloc at ../src/dlmalloc.c:3515
 #3 dlmalloc at ../src/dlmalloc.c:4245
 #4 ffi_closure_alloc at ../src/closures.c:572
 #5 bind_ffi_closure at virtual.c:2653
 #6 init_wrapper_funcs at virtual.c:2694
 #7 p11_virtual_wrap at virtual.c:2746
 #8 prepare_module_inlock_reentrant at modules.c:1778
 #9 p11_modules_load_inlock_reentrant at modules.c:1836
Comment 1 mdmpsyd@gmail.com 2013-12-23 23:28:44 UTC 
Created attachment 840965 [details]
File: backtrace
Comment 2 mdmpsyd@gmail.com 2013-12-23 23:28:45 UTC 
Created attachment 840966 [details]
File: cgroup
Comment 3 mdmpsyd@gmail.com 2013-12-23 23:28:47 UTC 
Created attachment 840967 [details]
File: core_backtrace
Comment 4 mdmpsyd@gmail.com 2013-12-23 23:28:49 UTC 
Created attachment 840968 [details]
File: dso_list
Comment 5 mdmpsyd@gmail.com 2013-12-23 23:28:50 UTC 
Created attachment 840969 [details]
File: environ
Comment 6 mdmpsyd@gmail.com 2013-12-23 23:28:52 UTC 
Created attachment 840970 [details]
File: exploitable
Comment 7 mdmpsyd@gmail.com 2013-12-23 23:28:54 UTC 
Created attachment 840971 [details]
File: limits
Comment 8 mdmpsyd@gmail.com 2013-12-23 23:28:55 UTC 
Created attachment 840972 [details]
File: maps
Comment 9 mdmpsyd@gmail.com 2013-12-23 23:28:57 UTC 
Created attachment 840973 [details]
File: open_fds
Comment 10 mdmpsyd@gmail.com 2013-12-23 23:28:59 UTC 
Created attachment 840974 [details]
File: proc_pid_status
Comment 11 mdmpsyd@gmail.com 2013-12-23 23:29:00 UTC 
Created attachment 840975 [details]
File: var_log_messages
Comment 12 Stef Walter 2014-01-15 13:32:59 UTC 
Thanks for reporting this bug. The trace points toward memory problems.

If you are able, and on the off chance that this bug is reproducable, Could you run the command line under valgrind, and post the output?

/usr/bin/trust extract --format=openssl-bundle --filter=certificates --overwrite /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt
Comment 13 Stef Walter 2014-08-07 06:53:17 UTC 
It's very likely that the info request above won't be filled by the original reporter, since this came in via abrt.

We'll probably need to wait for further info and/or bug reports that we can correlate this with in order to fix the issue.
Comment 14 Anthony Green 2018-03-18 14:02:48 UTC 
For what it's worth, I believe this was a bug in libffi that was just fixed upstream with this: https://github.com/libffi/libffi/commit/d46406088d28b038a0a0f7396d9621f431482f6a