From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: "François Revol" <revol@free.fr>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] vdi: Fix image opening and creation for odd disk sizes
Date: Tue, 11 May 2010 09:52:22 +0200 [thread overview]
Message-ID: <4BE90CB6.50709@redhat.com> (raw)
In-Reply-To: <1273522353-12851-1-git-send-email-weil@mail.berlios.de>
Am 10.05.2010 22:12, schrieb Stefan Weil:
> The fix is based on a patch from Kevin Wolf. Here his comment:
>
> "The number of blocks needs to be rounded up to cover all of the virtual hard
> disk. Without this fix, we can't even open our own images if their size is not
> a multiple of the block size."
>
> While Kevin's patch addressed vdi_create, my modification also fixes
> vdi_open which now accepts images with odd disk sizes as well as
> images created with old versions of qemu-img.
>
> Cc: Kevin Wolf <kwolf@redhat.com>
> Cc: François Revol <revol@free.fr>
> Signed-off-by: Stefan Weil <weil@mail.berlios.de>
> ---
> block/vdi.c | 29 +++++++++++++++++++++--------
> 1 files changed, 21 insertions(+), 8 deletions(-)
>
> diff --git a/block/vdi.c b/block/vdi.c
> index 1ce18d5..362c898 100644
> --- a/block/vdi.c
> +++ b/block/vdi.c
> @@ -405,19 +405,12 @@ static int vdi_open(BlockDriverState *bs, int flags)
> /* We only support data blocks which start on a sector boundary. */
> logout("unsupported data offset 0x%x B\n", header.offset_data);
> goto fail;
> - } else if (header.disk_size % SECTOR_SIZE != 0) {
> - logout("unsupported disk size %" PRIu64 " B\n", header.disk_size);
> - goto fail;
> } else if (header.sector_size != SECTOR_SIZE) {
> logout("unsupported sector size %u B\n", header.sector_size);
> goto fail;
> } else if (header.block_size != 1 * MiB) {
> logout("unsupported block size %u B\n", header.block_size);
> goto fail;
> - } else if ((header.disk_size + header.block_size - 1) / header.block_size !=
> - (uint64_t)header.blocks_in_image) {
> - logout("unexpected block number %u B\n", header.blocks_in_image);
> - goto fail;
> } else if (!uuid_is_null(header.uuid_link)) {
> logout("link uuid != 0, unsupported\n");
> goto fail;
> @@ -426,6 +419,23 @@ static int vdi_open(BlockDriverState *bs, int flags)
> goto fail;
> }
>
> + if (header.disk_size % SECTOR_SIZE != 0) {
> + /* 'VBoxManage convertfromraw' can create images with odd disk sizes.
> + We accept them but round the disk size to the next multiple of
> + SECTOR_SIZE. */
> + logout("odd disk size %" PRIu64 " B, round up\n", header.disk_size);
> + header.disk_size += SECTOR_SIZE - 1;
> + header.disk_size &= ~(SECTOR_SIZE - 1);
> + }
> +
> + if (header.disk_size >
> + (uint64_t)header.blocks_in_image * header.block_size) {
> + /* Old versions of qemu-img could create images with too large
> + disk sizes. We accept them but truncate the disk size. */
> + logout("large disk size %" PRIu64 " B, truncated\n", header.disk_size);
> + header.disk_size = (uint64_t)header.blocks_in_image * header.block_size;
> + }
I don't think this is useful behaviour. Such images are broken and
should not be opened. While it's true that qemu-img could create such
images, qemu could never open them afterwards, so nobody can have used
them anyway. So I think a goto fail; is the right thing to do.
Otherwise the patch looks good to me now.
Kevin
next prev parent reply other threads:[~2010-05-11 7:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 12:55 [Qemu-devel] [PATCH] vdi: Fix image creation Kevin Wolf
2010-05-06 18:05 ` [Qemu-devel] " Stefan Weil
2010-05-06 18:29 ` [Qemu-devel] [PATCH] vdi: Fix image opening and creation for odd disk sizes Stefan Weil
2010-05-07 7:55 ` [Qemu-devel] " Kevin Wolf
2010-05-07 11:55 ` François Revol
2010-05-09 10:17 ` Stefan Weil
2010-05-10 7:47 ` Kevin Wolf
2010-05-10 20:12 ` [Qemu-devel] " Stefan Weil
2010-05-10 20:44 ` [Qemu-devel] " François Revol
2010-05-11 7:52 ` Kevin Wolf [this message]
2010-05-12 18:25 ` [Qemu-devel] [PATCH] block/vdi: " Stefan Weil
2010-05-12 18:56 ` [Qemu-devel] " Kevin Wolf
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=4BE90CB6.50709@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=revol@free.fr \
--cc=weil@mail.berlios.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).