From: Amit Shah <amit.shah@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: "Li, Liang Z" <liang.z.li@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"quintela@redhat.com" <quintela@redhat.com>,
"berrange@redhat.com" <berrange@redhat.com>,
peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH] migration: fix live migration failure with compression
Date: Thu, 11 Aug 2016 10:07:30 +0530 [thread overview]
Message-ID: <20160811043730.GA12933@grmbl.mre> (raw)
In-Reply-To: <20160810175821.GH3172@work-vm>
On (Wed) 10 Aug 2016 [18:58:21], Dr. David Alan Gilbert wrote:
> * Li, Liang Z (liang.z.li@intel.com) wrote:
> > > Subject: Re: [PATCH] migration: fix live migration failure with compression
> > >
> > > * 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;
> > > > }
> >
> > 'qemu_put_be32' is used to put some data to an allocated 'f_src'. Before the 11808bb0c422, this operation
> > won't increase the 'f_src->iovcnt', there is no issue.
> > Commit 11808bb0c422 remove the checking of 'f->ops->writev_buffer',
> > now 'qemu_put_be32' will increase 'f_src->iovcnt' and set 'f_src->iov []', once the 'f_src->iovcnt' reach to
> > MAX_IOV_SIZE, 'qemu_fflush' will be trigged. Beacause 'f_src' is not writeable, 'qemu_fflsh' will return
> > without wrapping around 'f_src->iovcnt' , the following 'qemu_put_be32' on 'f_src' will increase 'f_src->iovcnt'
> > and make it exceed MAX_IOV_SIZE, then set 'f_src->iov[]' will corrupt memory.
>
> OK, thanks
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Did you mean to Reviewed-by?
> Amit, Peter: I think this is one for 2.7 because I think that's a regression
> given that the 11808bb0c422 referenced is after 2.6.
I'll send it out, thanks.
Amit
next prev parent reply other threads:[~2016-08-11 4:37 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
2016-08-10 6:16 ` Li, Liang Z
2016-08-10 17:58 ` Dr. David Alan Gilbert
2016-08-11 4:37 ` Amit Shah [this message]
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=20160811043730.GA12933@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=liang.z.li@intel.com \
--cc=peter.maydell@linaro.org \
--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 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).