Bug 903282
Summary: | libvirtd from git segfaults on shutdown in _dbus_warn_check_failed | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Eric Blake <eblake> |
Component: | libvirt | Assignee: | Eric Blake <eblake> |
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | CC: | acathrow, berrange, bili, clalancette, cwei, dallan, dyuan, eblake, itamar, jforbes, laine, libvirt-maint, mzhan, rjones, veillard, virt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 903184 | Environment: | |
Last Closed: | 2014-04-04 22:56:10 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: | |||
Bug Depends On: | 903184 | ||
Bug Blocks: |
Description
Eric Blake
2013-01-23 16:09:51 UTC
I've confirmed that the bug was introduced in v0.10.0 (commit f8ab364), and therefore RHEL 6.4 is vulnerable. However, the bug is masked by the fact that we don't clean up properly, so I'm not sure how urgent it is to backport a fix. The backport would consist of the following patches (already upstream, and also in upstream v0.10.2-maint): aafe419 - drop dead code introduced in commit f8ab364 47e1767 - expose the latent problem abbec81 - fix the actual bug I can't see anything critical to clean up during virStateCleanup(), and without that patch, we don't crash; so I think this patch is not urgent, and best picked up in 6.5. Since we will rebase for 6.5, I'm moving this to post. http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-June/msg00027.html if backporting rather than rebasing Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. |