Red Hat Bugzilla – Bug 1452752
Some block drivers incorrectly close their associated file
Last modified: 2017-08-02 00:41:00 EDT
Description of problem: Some block drivers (namely blkdebug, blkverify, blkreplay) sometiems close their assocated file node if an error occurs during initialization. This is unnecessary, and the way this is done is incorrect, leading to potentially invalid memory accesses. Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.9.0-5.el7 How reproducible: Always. Steps to Reproduce: $ qemu-img info --image-opts driver=blkdebug,image.driver=null-co,align=42 Actual results: [1] 23725 segmentation fault (core dumped) qemu-img info --image-opts driver=blkdebug,image.driver=null-co,align=42 Expected results: qemu-img: Could not open 'driver=blkdebug,image.driver=null-co,align=42': Invalid alignment Additional info: Fixed in upstream commit de234897b60e034ba94b307fc289e2dc692c9251.
Fix included in qemu-kvm-rhev-2.9.0-6.el7
Verified the issue with below packages: kernel-3.10.0-671.el7.x86_64 qemu-kvm-rhev-2.9.0-6.el7 Test steps: # qemu-img info --image-opts driver=blkdebug,image.driver=null-co,align=42 qemu-img: Could not open 'driver=blkdebug,image.driver=null-co,align=42': Invalid alignment
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://access.redhat.com/errata/RHSA-2017:2392