From: Stefan Hajnoczi <stefanha@gmail.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@parallels.com>
Cc: amit.shah@redhat.com, den@openvz.org, qemu-stable@nongnu.org,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/1] migration/block: fix pending() return value
Date: Fri, 2 Jan 2015 16:23:08 +0000 [thread overview]
Message-ID: <20150102162308.GP10823@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1419933856-4018-2-git-send-email-vsementsov@parallels.com>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On Tue, Dec 30, 2014 at 01:04:16PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Because of wrong return value of .save_live_pending() in
> migration/block.c, migration finishes before the whole disk is
> transferred. Such situation occurs when the migration process is fast
> enough, for example when source and dest are on the same host.
>
> If in the bulk phase we return something < max_size, we will skip
> transferring the tail of the device. Currently we have "set pending to
> BLOCK_SIZE if it is zero" for bulk phase, but there no guarantee, that
> it will be < max_size.
>
> True approach is to return, for example, max_size+1 when we are in the
> bulk phase.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@parallels.com>
> ---
> migration/block.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Yikes, this is a nasty bug. CCing qemu-stable.
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-01-02 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 10:04 [Qemu-devel] [PATCH v2 0/1] Fix block migration bug Vladimir Sementsov-Ogievskiy
2014-12-30 10:04 ` [Qemu-devel] [PATCH v2 1/1] migration/block: fix pending() return value Vladimir Sementsov-Ogievskiy
2015-01-02 16:23 ` Stefan Hajnoczi [this message]
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=20150102162308.GP10823@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=amit.shah@redhat.com \
--cc=den@openvz.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=quintela@redhat.com \
--cc=vsementsov@parallels.com \
/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).