From: Kevin Wolf <kwolf@redhat.com>
To: Pierre Riteau <Pierre.Riteau@irisa.fr>
Cc: qemu-devel@nongnu.org, tamura.yoshiaki@lab.ntt.co.jp
Subject: Re: [Qemu-devel] [PATCH] Fix block migration when the device size is not a multiple of 1 MB
Date: Fri, 21 Jan 2011 10:16:58 +0100 [thread overview]
Message-ID: <4D394F0A.9020608@redhat.com> (raw)
In-Reply-To: <1295449188-17877-1-git-send-email-Pierre.Riteau@irisa.fr>
Am 19.01.2011 15:59, schrieb Pierre Riteau:
> b02bea3a85cc939f09aa674a3f1e4f36d418c007 added a check on the return
> value of bdrv_write and aborts migration when it fails. However, if the
> size of the block device to migrate is not a multiple of BLOCK_SIZE
> (currently 1 MB), the last bdrv_write will fail with -EIO.
>
> Fixed by calling bdrv_write with the correct size of the last block.
> ---
> block-migration.c | 16 +++++++++++++++-
> 1 files changed, 15 insertions(+), 1 deletions(-)
>
> diff --git a/block-migration.c b/block-migration.c
> index 1475325..eeb9c62 100644
> --- a/block-migration.c
> +++ b/block-migration.c
> @@ -635,6 +635,8 @@ static int block_load(QEMUFile *f, void *opaque, int version_id)
> int64_t addr;
> BlockDriverState *bs;
> uint8_t *buf;
> + int64_t total_sectors;
> + int nr_sectors;
>
> do {
> addr = qemu_get_be64(f);
> @@ -656,10 +658,22 @@ static int block_load(QEMUFile *f, void *opaque, int version_id)
> return -EINVAL;
> }
>
> + total_sectors = bdrv_getlength(bs) >> BDRV_SECTOR_BITS;
> + if (total_sectors <= 0) {
> + fprintf(stderr, "Error getting length of block device %s\n", device_name);
> + return -EINVAL;
> + }
Can you resend the patch with error_report(), as Yoshi mentioned?
Also, I would move the total_sectors calculation outside the loop -
though I have no idea how many iterations it typically has, so it might
not improve things a lot.
Kevin
next prev parent reply other threads:[~2011-01-21 9:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 14:59 [Qemu-devel] [PATCH] Fix block migration when the device size is not a multiple of 1 MB Pierre Riteau
2011-01-20 2:06 ` Yoshiaki Tamura
2011-01-20 6:49 ` Pierre Riteau
2011-01-20 16:18 ` Yoshiaki Tamura
2011-01-21 8:08 ` Pierre Riteau
2011-01-21 9:11 ` Kevin Wolf
2011-01-21 12:26 ` Yoshiaki Tamura
2011-01-21 12:15 ` Yoshiaki Tamura
2011-01-21 12:31 ` Kevin Wolf
2011-01-21 12:36 ` Yoshiaki Tamura
2011-01-21 12:40 ` Pierre Riteau
2011-01-21 13:59 ` Yoshiaki Tamura
2011-01-21 14:09 ` Kevin Wolf
2011-01-21 14:18 ` Yoshiaki Tamura
2011-01-21 14:14 ` Pierre Riteau
2011-01-21 14:21 ` Yoshiaki Tamura
2011-01-21 14:23 ` Pierre Riteau
2011-01-21 14:30 ` Yoshiaki Tamura
2011-01-21 14:48 ` Pierre Riteau
2011-01-21 9:16 ` Kevin Wolf [this message]
2011-01-21 11:38 ` Pierre Riteau
2011-01-21 11:45 ` 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=4D394F0A.9020608@redhat.com \
--to=kwolf@redhat.com \
--cc=Pierre.Riteau@irisa.fr \
--cc=qemu-devel@nongnu.org \
--cc=tamura.yoshiaki@lab.ntt.co.jp \
/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).