From: Stefan Hajnoczi <stefanha@gmail.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
famz@redhat.com, Jeff Cody <jcody@redhat.com>,
qemu-devel@nongnu.org, vsementsov@parallels.com,
Stefan Hajnoczi <stefanha@redhat.com>,
John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [RFC 4/9] block: keep bitmap if incremental backup job is cancelled
Date: Thu, 25 Jun 2015 13:51:26 +0100 [thread overview]
Message-ID: <20150625125126.GE4419@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <558AEA49.8050808@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
On Wed, Jun 24, 2015 at 07:35:05PM +0200, Max Reitz wrote:
> On 12.06.2015 12:09, Stefan Hajnoczi wrote:
> >Reclaim the dirty bitmap if an incremental backup block job is
> >cancelled. The ret variable may be 0 when the job is cancelled so it's
> >not enough to check ret < 0.
> >
> >Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> >---
> > block/backup.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/block/backup.c b/block/backup.c
> >index d3f648d..c1ad975 100644
> >--- a/block/backup.c
> >+++ b/block/backup.c
> >@@ -430,7 +430,7 @@ static void coroutine_fn backup_run(void *opaque)
> > if (job->sync_bitmap) {
> > BdrvDirtyBitmap *bm;
> >- if (ret < 0) {
> >+ if (ret < 0 || block_job_is_cancelled(&job->common)) {
> > /* Merge the successor back into the parent, delete nothing. */
> > bm = bdrv_reclaim_dirty_bitmap(bs, job->sync_bitmap, NULL);
> > assert(bm);
>
> Since I can't find a seperate patch on qemu-devel or qemu-block yet:
>
> Reviewed-by: Max Reitz <mreitz@redhat.com>
Thanks, I must have gotten distracted before sending the email.
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-06-25 12:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 10:09 [Qemu-devel] [RFC 0/9] block: incremental backup transactions using BlockJobTxn Stefan Hajnoczi
2015-06-12 10:09 ` [Qemu-devel] [RFC 1/9] qapi: Add transaction support to block-dirty-bitmap operations Stefan Hajnoczi
2015-06-12 10:09 ` [Qemu-devel] [RFC 2/9] iotests: add transactional incremental backup test Stefan Hajnoczi
2015-06-12 10:09 ` [Qemu-devel] [RFC 3/9] block: rename BlkTransactionState and BdrvActionOps Stefan Hajnoczi
2015-06-12 10:09 ` [Qemu-devel] [RFC 4/9] block: keep bitmap if incremental backup job is cancelled Stefan Hajnoczi
2015-06-12 22:39 ` John Snow
2015-06-15 14:48 ` Stefan Hajnoczi
2015-06-24 17:35 ` Max Reitz
2015-06-25 12:51 ` Stefan Hajnoczi [this message]
2015-06-12 10:09 ` [Qemu-devel] [RFC 5/9] block: add block job transactions Stefan Hajnoczi
2015-06-24 18:37 ` Max Reitz
2015-06-25 12:50 ` Stefan Hajnoczi
2015-06-12 10:09 ` [Qemu-devel] [RFC 6/9] blockdev: make BlockJobTxn available to qmp 'transaction' Stefan Hajnoczi
2015-06-12 10:09 ` [Qemu-devel] [RFC 7/9] block/backup: support block job transactions Stefan Hajnoczi
2015-06-12 10:09 ` [Qemu-devel] [RFC 8/9] iotests: 124 - transactional failure test Stefan Hajnoczi
2015-06-12 10:09 ` [Qemu-devel] [RFC 9/9] qmp-commands.hx: Update the supported 'transaction' operations Stefan Hajnoczi
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=20150625125126.GE4419@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@parallels.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).