From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Liang Li <liang.z.li@intel.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com, amit.shah@redhat.com,
berrange@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: fix live migration failure with compression
Date: Tue, 9 Aug 2016 16:46:35 +0100 [thread overview]
Message-ID: <20160809154635.GD2025@work-vm> (raw)
In-Reply-To: <1470702146-24399-1-git-send-email-liang.z.li@intel.com>
* Liang Li (liang.z.li@intel.com) wrote:
> Because of commit 11808bb0c422, which remove some condition checks
> of 'f->ops->writev_buffer', 'qemu_put_qemu_file' should be enhanced
> to clear the 'f_src->iovcnt', or 'f_src->iovcnt' may exceed the
> MAX_IOV_SIZE which will break live migration. This should be fixed.
>
> Signed-off-by: Liang Li <liang.z.li@intel.com>
> Reported-by: Jinshi Zhang <jinshi.c.zhang@intel.com>
> ---
> migration/qemu-file.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/migration/qemu-file.c b/migration/qemu-file.c
> index bbc565e..e9fae31 100644
> --- a/migration/qemu-file.c
> +++ b/migration/qemu-file.c
> @@ -668,6 +668,7 @@ int qemu_put_qemu_file(QEMUFile *f_des, QEMUFile *f_src)
> len = f_src->buf_index;
> qemu_put_buffer(f_des, f_src->buf, f_src->buf_index);
> f_src->buf_index = 0;
> + f_src->iovcnt = 0;
> }
If you're just using the buf[] in the src, how does it end up incrementing
the iovcnt?
Dave
> return len;
> }
> --
> 1.9.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-08-09 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 0:22 [Qemu-devel] [PATCH] migration: fix live migration failure with compression Liang Li
2016-08-09 15:46 ` Dr. David Alan Gilbert [this message]
2016-08-10 6:16 ` Li, Liang Z
2016-08-10 17:58 ` Dr. David Alan Gilbert
2016-08-11 4:37 ` Amit Shah
2016-08-11 8:03 ` Dr. David Alan Gilbert
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=20160809154635.GD2025@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=berrange@redhat.com \
--cc=liang.z.li@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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.