From: John Snow <jsnow@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com, John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] [PATCH 1/3] block: prohibit migration during BlockJobs
Date: Thu, 1 Oct 2015 12:34:31 -0400 [thread overview]
Message-ID: <1443717273-5280-2-git-send-email-jsnow@redhat.com> (raw)
In-Reply-To: <1443717273-5280-1-git-send-email-jsnow@redhat.com>
Unless we can prove this to be safe for specific cases,
the default should be to prohibit migration during BlockJobs.
In conjunction with
"migration: disallow_migrate_add_blocker during migration",
this should be sufficient to disallow the blockjob from starting
in the event of an in-progress migration.
Signed-off-by: John Snow <jsnow@redhat.com>
---
blockjob.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/blockjob.c b/blockjob.c
index 62bb906..b5849b3 100644
--- a/blockjob.c
+++ b/blockjob.c
@@ -35,12 +35,14 @@
#include "qmp-commands.h"
#include "qemu/timer.h"
#include "qapi-event.h"
+#include "migration/migration.h"
void *block_job_create(const BlockJobDriver *driver, BlockDriverState *bs,
int64_t speed, BlockCompletionFunc *cb,
void *opaque, Error **errp)
{
BlockJob *job;
+ int ret;
if (bs->job) {
error_setg(errp, QERR_DEVICE_IN_USE, bdrv_get_device_name(bs));
@@ -71,6 +73,14 @@ void *block_job_create(const BlockJobDriver *driver, BlockDriverState *bs,
return NULL;
}
}
+
+ /* Re-use the op-blocker as a migration blocker */
+ ret = migrate_add_blocker(job->blocker, errp);
+ if (ret < 0) {
+ block_job_release(bs);
+ return NULL;
+ }
+
return job;
}
@@ -80,6 +90,7 @@ void block_job_release(BlockDriverState *bs)
bs->job = NULL;
bdrv_op_unblock_all(bs, job->blocker);
+ migrate_del_blocker(job->blocker);
error_free(job->blocker);
g_free(job);
}
--
2.4.3
next prev parent reply other threads:[~2015-10-01 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 16:34 [Qemu-devel] [PATCH 0/3] block: prohibit migrations during tasks John Snow
2015-10-01 16:34 ` John Snow [this message]
2015-10-01 18:03 ` [Qemu-devel] [PATCH 1/3] block: prohibit migration during BlockJobs Paolo Bonzini
2015-10-02 18:17 ` John Snow
2015-10-05 8:13 ` Kevin Wolf
2015-10-05 14:55 ` Paolo Bonzini
2015-10-01 16:34 ` [Qemu-devel] [PATCH 2/3] block/mirror: allow migration after sync John Snow
2015-10-01 16:34 ` [Qemu-devel] [PATCH 3/3] block: prohibit migration during transactions John Snow
2015-10-01 18:01 ` Paolo Bonzini
2015-10-02 18:20 ` John Snow
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=1443717273-5280-2-git-send-email-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).