Bug 827127 - double-close bugs in libvirt
double-close bugs in libvirt
Product: Fedora
Classification: Fedora
Component: libvirt (Show other bugs)
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Libvirt Maintainers
Fedora Extras Quality Assurance
Depends On: 823716 827125
  Show dependency treegraph
Reported: 2012-05-31 13:02 EDT by Eric Blake
Modified: 2013-01-10 23:13 EST (History)
32 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 827125
Last Closed: 2012-07-05 19:45:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Comment 1 Eric Blake 2012-05-31 13:03:19 EDT
We need six consecutive commits backported to F16, as this set of double-close bugs can cause rather insidious failures of libvirt.

b19c236d69278c967d2d8b4aae97ac76213f1c10 qemu: avoid closing fd more than once
746ff701e8727439cac8ca72531d82e5cb7fa129 command: check for fork error before closing fd
f3cfc7c8848006b613e09bb1acd081716854527e fdstream: avoid double close bug
da831afcf2f6c0d3ed1ea3128a6208f548a05d8f command: avoid double close bugs
655cffa0f25be40c68624036af80bde102177612 avoid fd leak
0a045f01cfa48fabd41c801e3f44034a4e6da485 avoid closing uninitialized fd
Comment 2 Fedora Update System 2012-06-24 19:55:23 EDT
libvirt- has been submitted as an update for Fedora 16.
Comment 3 Fedora Update System 2012-06-25 20:55:59 EDT
Package libvirt-
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libvirt-'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Comment 4 Fedora Update System 2012-07-05 19:45:10 EDT
libvirt- has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.