Bug 1328372

Summary: [abrt] device-mapper-event: _timeout_thread(): dmeventd killed by SIGSEGV
Product: Red Hat Enterprise Linux 7 Reporter: Matěj Cepl <mcepl>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
lvm2 sub component: Default / Unclassified QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: agk, heinzm, jbrassow, mcepl, msnitzer, prajnoha, prockai, rbednar, thornber, zkabelac
Version: 7.3   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://faf-report.itos.redhat.com/reports/bthash/27484ec470a07f5a27612dc84c6c6ebf69df6e1d
Whiteboard: abrt_hash:fb2d3cd4f3ca7f33ff5b127c9c9b4bfa66a40368
Fixed In Version: lvm2-2.02.162-1.el7 Doc Type: Bug Fix
Doc Text:
dmeventd code has been updated to recent version which includes numerous fixes, including fixes for various possible segfaults.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 04:20:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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: machineid
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: sosreport.tar.xz none

Description Matěj Cepl 2016-04-19 08:48:44 UTC 
Version-Release number of selected component:
device-mapper-event-1.02.107-5.el7_2.1

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/sbin/dmeventd -f
crash_function: _timeout_thread
executable:     /usr/sbin/dmeventd
global_pid:     1047
kernel:         3.10.0-377.el7.x86_64
runlevel:       unknown
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (1 frames)
 #0 _timeout_thread

Potential duplicate: bug 1220856
Comment 1 Matěj Cepl 2016-04-19 08:48:53 UTC 
Created attachment 1148404 [details]
File: backtrace
Comment 2 Matěj Cepl 2016-04-19 08:48:55 UTC 
Created attachment 1148405 [details]
File: cgroup
Comment 3 Matěj Cepl 2016-04-19 08:48:57 UTC 
Created attachment 1148406 [details]
File: core_backtrace
Comment 4 Matěj Cepl 2016-04-19 08:48:58 UTC 
Created attachment 1148407 [details]
File: dso_list
Comment 5 Matěj Cepl 2016-04-19 08:49:00 UTC 
Created attachment 1148408 [details]
File: environ
Comment 6 Matěj Cepl 2016-04-19 08:49:02 UTC 
Created attachment 1148409 [details]
File: exploitable
Comment 7 Matěj Cepl 2016-04-19 08:49:04 UTC 
Created attachment 1148410 [details]
File: limits
Comment 8 Matěj Cepl 2016-04-19 08:49:06 UTC 
Created attachment 1148411 [details]
File: machineid
Comment 9 Matěj Cepl 2016-04-19 08:49:08 UTC 
Created attachment 1148412 [details]
File: maps
Comment 10 Matěj Cepl 2016-04-19 08:49:10 UTC 
Created attachment 1148413 [details]
File: open_fds
Comment 11 Matěj Cepl 2016-04-19 08:49:12 UTC 
Created attachment 1148414 [details]
File: proc_pid_status
Comment 12 Matěj Cepl 2016-04-19 08:49:13 UTC 
Created attachment 1148415 [details]
File: var_log_messages
Comment 13 Matěj Cepl 2016-04-19 08:51:03 UTC 
Created attachment 1148417 [details]
File: sosreport.tar.xz
Comment 17 Peter Rajnoha 2016-06-03 12:24:20 UTC 
Currently, we have lvm2-2.02.152-2.el7 in 7.3 - please try this build and see if you can reproduce. Thanks.
Comment 18 Matěj Cepl 2016-06-13 13:13:15 UTC 
(In reply to Peter Rajnoha from comment #17)
> Currently, we have lvm2-2.02.152-2.el7 in 7.3 - please try this build and
> see if you can reproduce. Thanks.

You mean, lvm2-2.02.156-1, right?
Comment 19 Alasdair Kergon 2016-06-13 13:25:53 UTC 
"or whatever later version we built since"
Comment 21 Peter Rajnoha 2016-08-01 12:15:24 UTC 
For now, I'm assuming this is fixed with recent builds. If this problem appears again, please, reopen this bug report.
Comment 22 Roman Bednář 2016-08-01 12:34:22 UTC 
Adding QA ack for 7.3. SanityOnly, it's unlikely we'll be able to reproduce this. We can verify this bug after regression run is done without any dmeventd segfaults.
Comment 24 Roman Bednář 2016-09-21 12:21:04 UTC 
Verified - SanityOnly.

The issue did not occur during regression testing.

3.10.0-505.el7.x86_64

lvm2-2.02.165-2.el7    BUILT: Wed Sep 14 16:01:43 CEST 2016
lvm2-libs-2.02.165-2.el7    BUILT: Wed Sep 14 16:01:43 CEST 2016
lvm2-cluster-2.02.165-2.el7    BUILT: Wed Sep 14 16:01:43 CEST 2016
device-mapper-1.02.134-2.el7    BUILT: Wed Sep 14 16:01:43 CEST 2016
device-mapper-libs-1.02.134-2.el7    BUILT: Wed Sep 14 16:01:43 CEST 2016
device-mapper-event-1.02.134-2.el7    BUILT: Wed Sep 14 16:01:43 CEST 2016
device-mapper-event-libs-1.02.134-2.el7    BUILT: Wed Sep 14 16:01:43 CEST 2016
device-mapper-persistent-data-0.6.3-1.el7    BUILT: Fri Jul 22 12:29:13 CEST 2016
cmirror-2.02.165-2.el7    BUILT: Wed Sep 14 16:01:43 CEST 2016
Comment 26 errata-xmlrpc 2016-11-04 04:20:20 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://rhn.redhat.com/errata/RHBA-2016-1445.html