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 950599

Summary:	[abrt] libvirt-client-0.10.2-18.el6: remoteClientCloseFunc: Process /usr/bin/virsh was killed by signal 11 (SIGSEGV)
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Pelland <cpelland>
Component:	libvirt	Assignee:	Peter Krempa <pkrempa>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.4	CC:	abienven, acathrow, cpelland, dallan, djasa, dyasny, dyuan, eblake, mjenner, mzhan, pkrempa, pm-eus, rwu, ydu, zhwang
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:	libvirt-0.10.2-18.el6_4.4	Doc Type:	Bug Fix
Doc Text:	Due to a race condition in the libvirt client library, any application using libvirt could terminate unexpectedly with a segmentation fault. This happened when one thread executed the connection close callback, while another one freed the connection object, and the connection callback thread then accessed memory that had been already freed. This update fixes the possibility of freeing the callback data when they are still being accessed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-18 15:55:24 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:
Bug Depends On:	911609
Bug Blocks:

Description Chris Pelland 2013-04-10 13:24:08 UTC

This bug has been copied from bug #911609 and has been proposed
to be backported to 6.4 z-stream (EUS).

Comment 6 Eric Blake 2013-04-10 22:27:32 UTC

In POST:
http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-April/msg00211.html

Comment 8 yanbing du 2013-04-15 09:25:23 UTC

Download the src of libvirt-0.10.2-18.el6 libvirt-0.10.2-18.el6_4.4, then rebuild them with apply patch http://www.redhat.com/archives/libvir-list/2013-March/msg01683.html

Can reproduce it with libvirt-0.10.2-18.el6
# virsh list
 Id    Name                           State
----------------------------------------------------



 DEBUG: Connection close called, sleeping



 DEBUG: calling the close callback



 DEBUG: Finishing close

Segmentation fault (core dumped)

And verified this bug with libvirt-0.10.2-18.el6_4.4.

Comment 10 errata-xmlrpc 2013-04-18 15:55:24 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.

http://rhn.redhat.com/errata/RHBA-2013-0756.html