From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: do not probe zero-sized disks
Date: Thu, 10 Jan 2013 10:17:24 -0700 [thread overview]
Message-ID: <50EEF7A4.7090009@redhat.com> (raw)
In-Reply-To: <1357828767-2327-1-git-send-email-pbonzini@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On 01/10/2013 07:39 AM, Paolo Bonzini wrote:
> A blank CD or DVD is visible as a zero-sized disks. Probing such
> disks will lead to an EIO and a failure to start the VM. Treating
> them as raw is a better solution.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> block.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block.c b/block.c
> index c05875f..b9da10e 100644
> --- a/block.c
> +++ b/block.c
> @@ -532,7 +532,7 @@ static int find_image_format(const char *filename, BlockDriver **pdrv)
> }
>
> /* Return the raw BlockDriver * to scsi-generic devices or empty drives */
> - if (bs->sg || !bdrv_is_inserted(bs)) {
> + if (bs->sg || !bdrv_is_inserted(bs) || bdrv_getlength(bs) == 0) {
Do we need to extend this to all files with size smaller than the length
of the header used in probing to determine a non-raw file? Or is the
case of someone passing a 1-byte file as a backing file of a device too
unlikely, where refusing to start the VM is okay for that case?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2013-01-10 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 14:39 [Qemu-devel] [PATCH] block: do not probe zero-sized disks Paolo Bonzini
2013-01-10 15:17 ` Kevin Wolf
2013-01-10 17:17 ` Eric Blake [this message]
2013-01-11 9:33 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50EEF7A4.7090009@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.