From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
quintela@redhat.com, famz@redhat.com, stefanha@redhat.com,
den@openvz.org, jsnow@redhat.com, qemu-stable@nongnu.org,
eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration/block-dirty-bitmap: fix dirty_bitmap_load
Date: Fri, 15 Jun 2018 12:24:37 +0100 [thread overview]
Message-ID: <20180615112436.GC13796@work-vm> (raw)
In-Reply-To: <20180530112424.204835-1-vsementsov@virtuozzo.com>
* Vladimir Sementsov-Ogievskiy (vsementsov@virtuozzo.com) wrote:
> dirty_bitmap_load_header return code is obtained but not handled. Fix
> this.
>
> Bug was introduced in b35ebdf076d697bc
> "migration: add postcopy migration of dirty bitmaps" with the whole
> function.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Queued via migration
> ---
> migration/block-dirty-bitmap.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/migration/block-dirty-bitmap.c b/migration/block-dirty-bitmap.c
> index 8819aabe3a..2c541c985d 100644
> --- a/migration/block-dirty-bitmap.c
> +++ b/migration/block-dirty-bitmap.c
> @@ -672,6 +672,9 @@ static int dirty_bitmap_load(QEMUFile *f, void *opaque, int version_id)
>
> do {
> ret = dirty_bitmap_load_header(f, &s);
> + if (ret < 0) {
> + return ret;
> + }
>
> if (s.flags & DIRTY_BITMAP_MIG_FLAG_START) {
> ret = dirty_bitmap_load_start(f, &s);
> --
> 2.11.1
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2018-06-15 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 11:24 [Qemu-devel] [PATCH] migration/block-dirty-bitmap: fix dirty_bitmap_load Vladimir Sementsov-Ogievskiy
2018-05-30 15:22 ` Eric Blake
2018-05-30 20:25 ` John Snow
2018-06-15 11:24 ` Dr. David Alan Gilbert [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=20180615112436.GC13796@work-vm \
--to=dgilbert@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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).