Bug 1452702

Summary:	qemu-img aborts on empty filenames
Product:	Red Hat Enterprise Linux 7	Reporter:	Hanna Czenczek <hreitz>
Component:	qemu-kvm-rhev	Assignee:	Hanna Czenczek <hreitz>
Status:	CLOSED ERRATA	QA Contact:	Ping Li <pingl>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	aliang, chayang, coli, juzhang, michen, mrezanin, qzhang, virt-maint
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	qemu-kvm-rhev-2.9.0-6.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-02 04:41:00 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:

Description Hanna Czenczek 2017-05-19 13:47:38 UTC

Description of problem / steps to reproduce:

$ qemu-img info ''
qemu-img: block.c:1045: bdrv_open_driver: Assertion `!drv->bdrv_needs_filename || bs->filename[0]' failed.
[1]    14622 abort (core dumped)  ./qemu-img info ''


Version-Release number of selected component (if applicable):

qemu-kvm-rhev-2.9.0-5.el7


How reproducible:

Always


Expected results:

$ qemu-img info ''
qemu-img: Could not open '': The 'file' block driver requires a file name


Additional info:

Fixed in upstream commit 4a0082401a770261b85625a41eef4a4e89ad7a74.

Comment 2 Miroslav Rezanina 2017-05-23 08:16:47 UTC

Fix included in qemu-kvm-rhev-2.9.0-6.el7

Comment 4 Ping Li 2017-05-24 03:33:22 UTC

Verify 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 ''
qemu-img: Could not open '': The 'file' block driver requires a file name

Comment 6 errata-xmlrpc 2017-08-02 04:41:00 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://access.redhat.com/errata/RHSA-2017:2392