From: Sergio Lopez <slp@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, qemu-devel@nongnu.org,
Sergio Lopez <slp@redhat.com>,
mreitz@redhat.com
Subject: [Qemu-devel] [PATCH v2 1/2] blockdev: release the AioContext at drive_backup_prepare
Date: Fri, 13 Sep 2019 17:25:07 +0200 [thread overview]
Message-ID: <20190913152507.56197-2-slp@redhat.com> (raw)
In-Reply-To: <20190913152507.56197-1-slp@redhat.com>
do_drive_backup() already acquires the AioContext, so release it
before the call.
Signed-off-by: Sergio Lopez <slp@redhat.com>
---
blockdev.c | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/blockdev.c b/blockdev.c
index fbef6845c8..3927fdab80 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -1783,20 +1783,16 @@ static void drive_backup_prepare(BlkActionState *common, Error **errp)
aio_context = bdrv_get_aio_context(bs);
aio_context_acquire(aio_context);
-
/* Paired with .clean() */
bdrv_drained_begin(bs);
+ aio_context_release(aio_context);
state->bs = bs;
state->job = do_drive_backup(backup, common->block_job_txn, &local_err);
if (local_err) {
error_propagate(errp, local_err);
- goto out;
}
-
-out:
- aio_context_release(aio_context);
}
static void drive_backup_commit(BlkActionState *common)
--
2.21.0
next prev parent reply other threads:[~2019-09-13 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 15:25 [Qemu-devel] [PATCH v2 0/2] blockdev: avoid acquiring AioContext lock twice at do_drive_backup() Sergio Lopez
2019-09-13 15:25 ` Sergio Lopez [this message]
2019-09-13 19:54 ` [Qemu-devel] [Qemu-block] [PATCH v2 1/2] blockdev: release the AioContext at drive_backup_prepare John Snow
2019-09-16 7:53 ` Kevin Wolf
2019-09-16 11:17 ` Sergio Lopez
2019-10-03 9:33 ` Sergio Lopez
2019-10-10 15:02 ` Kevin Wolf
2019-09-16 11:17 ` [Qemu-devel] " Sergio Lopez
2019-09-13 15:25 ` [Qemu-devel] [PATCH v2 2/2] blockdev: honor bdrv_try_set_aio_context() context requirements Sergio Lopez
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=20190913152507.56197-2-slp@redhat.com \
--to=slp@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).