qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: John Snow <jsnow@redhat.com>,
	qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
	jtc@redhat.com, Jeff Cody <jcody@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 4/9] block/commit: utilize job_exit shim
Date: Mon, 27 Aug 2018 12:28:17 +0200	[thread overview]
Message-ID: <18f0d76d-cd66-26a7-ef81-a6b9ef1c6c80@redhat.com> (raw)
In-Reply-To: <20180823220856.10094-5-jsnow@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 756 bytes --]

On 2018-08-24 00:08, John Snow wrote:
> Change the manual deferment to commit_complete into the implicit
> callback to job_exit, renaming commit_complete to commit_exit.
> 
> This conversion does change the timing of when job_completed is
> called to after the bdrv_replace_node and bdrv_unref calls, which
> could have implications for bjob->blk which will now be put down
> after this cleanup.
> 
> Kevin highlights that we did not take any permissions for that backend
> at job creation time, so it is safe to reorder these operations.
> 
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
>  block/commit.c | 22 +++++-----------------
>  1 file changed, 5 insertions(+), 17 deletions(-)

Reviewed-by: Max Reitz <mreitz@redhat.com>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-08-27 10:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 22:08 [Qemu-devel] [PATCH v2 0/9] jobs: Job Exit Refactoring Pt 1 John Snow
2018-08-23 22:08 ` [Qemu-devel] [PATCH v2 1/9] jobs: change start callback to run callback John Snow
2018-08-27  9:30   ` Max Reitz
2018-08-30  0:06     ` John Snow
2018-08-31  9:06       ` Max Reitz
2018-08-23 22:08 ` [Qemu-devel] [PATCH v2 2/9] jobs: canonize Error object John Snow
2018-08-27  9:41   ` Max Reitz
2018-08-27 10:43     ` Max Reitz
2018-08-23 22:08 ` [Qemu-devel] [PATCH v2 3/9] jobs: add exit shim John Snow
2018-08-27 10:00   ` Max Reitz
2018-08-23 22:08 ` [Qemu-devel] [PATCH v2 4/9] block/commit: utilize job_exit shim John Snow
2018-08-27 10:28   ` Max Reitz [this message]
2018-08-23 22:08 ` [Qemu-devel] [PATCH v2 5/9] block/mirror: " John Snow
2018-08-27 10:30   ` Max Reitz
2018-08-23 22:08 ` [Qemu-devel] [PATCH v2 6/9] jobs: " John Snow
2018-08-27 10:37   ` Max Reitz
2018-08-23 22:08 ` [Qemu-devel] [PATCH v2 7/9] block/backup: make function variables consistently named John Snow
2018-08-27 10:41   ` Max Reitz
2018-08-23 22:08 ` [Qemu-devel] [PATCH v2 8/9] jobs: remove ret argument to job_completed; privatize it John Snow
2018-08-27 10:52   ` Max Reitz
2018-08-27 18:43     ` John Snow
2018-08-23 22:08 ` [Qemu-devel] [PATCH v2 9/9] jobs: remove job_defer_to_main_loop John Snow
2018-08-27 10:56   ` Max Reitz

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=18f0d76d-cd66-26a7-ef81-a6b9ef1c6c80@redhat.com \
    --to=mreitz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=jtc@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).