From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org, Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Peter Krempa <pkrempa@redhat.com>
Subject: Re: [RFC v2] migration: Add migrate-set-bitmap-node-mapping
Date: Thu, 14 May 2020 09:42:42 +0100 [thread overview]
Message-ID: <20200514084242.GB2787@work-vm> (raw)
In-Reply-To: <20200513145610.1484567-1-mreitz@redhat.com>
* Max Reitz (mreitz@redhat.com) wrote:
<snip>
> +void qmp_migrate_set_bitmap_node_mapping(MigrationBlockNodeMappingList *mapping,
> + Error **errp)
> +{
> + QDict *in_mapping = qdict_new();
> + QDict *out_mapping = qdict_new();
> +
> + for (; mapping; mapping = mapping->next) {
> + MigrationBlockNodeMapping *entry = mapping->value;
> +
> + if (qdict_haskey(out_mapping, entry->node_name)) {
> + error_setg(errp, "Cannot map node name '%s' twice",
> + entry->node_name);
> + goto fail;
> + }
I'm not too clear exactly which case this is protecting against;
I think that's protecting against mapping
'src1'->'dst1' and 'src1'->'dst2'
which is a good check.s (or maybe it's checking against dst2 twice?)
What about cases where there is no mapping - e.g. imagine
that we have b1/b2 on the source and b2/b3 on the dest; now
if we add just a mapping:
b1->b2
then we end up with:
b1 -> b2
b2 -> b2 (non-mapped)
b3
so we have a clash there - are we protected against that?
Dave
> + if (qdict_haskey(in_mapping, entry->alias)) {
> + error_setg(errp, "Cannot use alias '%s' twice",
> + entry->alias);
> + goto fail;
> + }
> +
> + qdict_put_str(in_mapping, entry->alias, entry->node_name);
> + qdict_put_str(out_mapping, entry->node_name, entry->alias);
> + }
> +
> + qobject_unref(dirty_bitmap_mig_state.node_in_mapping);
> + qobject_unref(dirty_bitmap_mig_state.node_out_mapping);
> +
> + dirty_bitmap_mig_state.node_in_mapping = in_mapping;
> + dirty_bitmap_mig_state.node_out_mapping = out_mapping;
> +
> + return;
> +
> +fail:
> + qobject_unref(in_mapping);
> + qobject_unref(out_mapping);
> +}
> +
> static SaveVMHandlers savevm_dirty_bitmap_handlers = {
> .save_setup = dirty_bitmap_save_setup,
> .save_live_complete_postcopy = dirty_bitmap_save_complete,
> --
> 2.26.2
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-05-14 8:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 14:56 [RFC v2] migration: Add migrate-set-bitmap-node-mapping Max Reitz
2020-05-13 16:11 ` Eric Blake
2020-05-14 7:13 ` Max Reitz
2020-05-14 11:07 ` Kevin Wolf
2020-05-13 20:09 ` Vladimir Sementsov-Ogievskiy
2020-05-14 7:42 ` Max Reitz
2020-05-14 9:09 ` Max Reitz
2020-05-14 10:58 ` Vladimir Sementsov-Ogievskiy
2020-05-14 11:04 ` Kevin Wolf
2020-05-14 8:42 ` Dr. David Alan Gilbert [this message]
2020-05-14 9:08 ` Max Reitz
2020-05-14 9:32 ` Dr. David Alan Gilbert
2020-05-18 16:26 ` Peter Krempa
2020-05-18 17:52 ` Vladimir Sementsov-Ogievskiy
2020-05-18 18:20 ` Peter Krempa
2020-05-18 18:47 ` Vladimir Sementsov-Ogievskiy
2020-06-02 10:56 ` Max Reitz
2020-06-02 11:12 ` Peter Krempa
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=20200514084242.GB2787@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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.