From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, imain@redhat.com,
stefanha@redhat.com, pbonzini@redhat.com
Subject: [Qemu-devel] [RFC PATCH 1/4] block/backup: delete target after completion callback
Date: Mon, 29 Jul 2013 12:25:29 +0800 [thread overview]
Message-ID: <1375071932-31627-2-git-send-email-famz@redhat.com> (raw)
In-Reply-To: <1375071932-31627-1-git-send-email-famz@redhat.com>
Move bdrv_delete(target) one line down to give block job caller a chance
to handle target on completion before deleting it.
Signed-off-by: Fam Zheng <famz@redhat.com>
---
block/backup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/backup.c b/block/backup.c
index 6ae8a05..d80341c 100644
--- a/block/backup.c
+++ b/block/backup.c
@@ -338,9 +338,9 @@ static void coroutine_fn backup_run(void *opaque)
hbitmap_free(job->bitmap);
bdrv_iostatus_disable(target);
- bdrv_delete(target);
block_job_completed(&job->common, ret);
+ bdrv_delete(target);
}
void backup_start(BlockDriverState *bs, BlockDriverState *target,
--
1.8.3.4
next prev parent reply other threads:[~2013-07-29 4:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 4:25 [Qemu-devel] [RFC PATCH 0/4] hmp/qmp: add snapshot option to nbd export Fam Zheng
2013-07-29 4:25 ` Fam Zheng [this message]
2013-08-21 18:37 ` [Qemu-devel] [RFC PATCH 1/4] block/backup: delete target after completion callback Eric Blake
2013-07-29 4:25 ` [Qemu-devel] [RFC PATCH 2/4] nbd: call drive_put_ref() only if dinfo exists Fam Zheng
2013-08-21 12:47 ` Stefan Hajnoczi
2013-07-29 4:25 ` [Qemu-devel] [RFC PATCH 3/4] qmp: Add "snapshot=" option to nbd-server-add Fam Zheng
2013-08-21 13:02 ` Stefan Hajnoczi
2013-08-21 18:40 ` Eric Blake
2013-08-22 8:53 ` Fam Zheng
2013-08-22 9:22 ` Paolo Bonzini
2013-08-22 9:42 ` Fam Zheng
2013-08-26 8:07 ` Fam Zheng
2013-08-21 18:42 ` Eric Blake
2013-07-29 4:25 ` [Qemu-devel] [RFC PATCH 4/4] hmp: add -s switch to nbd_server_add Fam Zheng
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=1375071932-31627-2-git-send-email-famz@redhat.com \
--to=famz@redhat.com \
--cc=imain@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--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).