From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <fam@euphon.net>,
qemu-devel@nongnu.org,
Emanuele Giuseppe Esposito <eesposit@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Subject: [PATCH v2 6/8] block: do not acquire AioContext in check_to_replace_node
Date: Mon, 19 Apr 2021 10:55:39 +0200 [thread overview]
Message-ID: <20210419085541.22310-7-eesposit@redhat.com> (raw)
In-Reply-To: <20210419085541.22310-1-eesposit@redhat.com>
Make the (only) caller do it.
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
---
block.c | 22 +++++-----------------
blockdev.c | 7 ++++++-
include/block/block.h | 1 +
3 files changed, 12 insertions(+), 18 deletions(-)
diff --git a/block.c b/block.c
index f40fb63c75..fd12f88062 100644
--- a/block.c
+++ b/block.c
@@ -6776,24 +6776,15 @@ bool bdrv_recurse_can_replace(BlockDriverState *bs,
*
* The result (whether the node can be replaced or not) is only valid
* for as long as no graph or permission changes occur.
+ *
+ * Called with AioContext lock held.
*/
BlockDriverState *check_to_replace_node(BlockDriverState *parent_bs,
+ BlockDriverState *to_replace_bs,
const char *node_name, Error **errp)
{
- BlockDriverState *to_replace_bs = bdrv_find_node(node_name);
- AioContext *aio_context;
-
- if (!to_replace_bs) {
- error_setg(errp, "Failed to find node with node-name='%s'", node_name);
- return NULL;
- }
-
- aio_context = bdrv_get_aio_context(to_replace_bs);
- aio_context_acquire(aio_context);
-
if (bdrv_op_is_blocked(to_replace_bs, BLOCK_OP_TYPE_REPLACE, errp)) {
- to_replace_bs = NULL;
- goto out;
+ return NULL;
}
/* We don't want arbitrary node of the BDS chain to be replaced only the top
@@ -6806,12 +6797,9 @@ BlockDriverState *check_to_replace_node(BlockDriverState *parent_bs,
"because it cannot be guaranteed that doing so would not "
"lead to an abrupt change of visible data",
node_name, parent_bs->node_name);
- to_replace_bs = NULL;
- goto out;
+ return NULL;
}
-out:
- aio_context_release(aio_context);
return to_replace_bs;
}
diff --git a/blockdev.c b/blockdev.c
index a57590aae4..e901107344 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -3056,13 +3056,18 @@ static void blockdev_mirror_common(const char *job_id, BlockDriverState *bs,
return;
}
- to_replace_bs = check_to_replace_node(bs, replaces, errp);
+ to_replace_bs = bdrv_find_node(replaces);
if (!to_replace_bs) {
+ error_setg(errp, "Failed to find node with node-name='%s'",
+ replaces);
return;
}
replace_aio_context = bdrv_get_aio_context(to_replace_bs);
aio_context_acquire(replace_aio_context);
+ if (!check_to_replace_node(bs, to_replace_bs, replaces, errp)) {
+ return;
+ }
replace_size = bdrv_getlength(to_replace_bs);
aio_context_release(replace_aio_context);
diff --git a/include/block/block.h b/include/block/block.h
index b3f6e509d4..f57c34a19a 100644
--- a/include/block/block.h
+++ b/include/block/block.h
@@ -474,6 +474,7 @@ int bdrv_amend_options(BlockDriverState *bs_new, QemuOpts *opts,
/* check if a named node can be replaced when doing drive-mirror */
BlockDriverState *check_to_replace_node(BlockDriverState *parent_bs,
+ BlockDriverState *to_replace_bs,
const char *node_name, Error **errp);
/* async block I/O */
--
2.30.2
next prev parent reply other threads:[~2021-04-19 8:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 8:55 [PATCH v2 0/8] Block layer thread-safety, continued Emanuele Giuseppe Esposito
2021-04-19 8:55 ` [PATCH v2 1/8] block: prepare write threshold code for thread safety Emanuele Giuseppe Esposito
2021-05-05 8:50 ` Stefan Hajnoczi
2021-05-05 9:54 ` Vladimir Sementsov-Ogievskiy
2021-05-06 9:04 ` Stefan Hajnoczi
2021-05-06 9:14 ` Vladimir Sementsov-Ogievskiy
2021-04-19 8:55 ` [PATCH v2 2/8] block: protect write threshold QMP commands from concurrent requests Emanuele Giuseppe Esposito
2021-05-05 8:55 ` Stefan Hajnoczi
2021-05-05 11:29 ` Paolo Bonzini
2021-04-19 8:55 ` [PATCH v2 3/8] util: use RCU accessors for notifiers Emanuele Giuseppe Esposito
2021-05-05 9:47 ` Stefan Hajnoczi
2021-04-19 8:55 ` [PATCH v2 4/8] block: make before-write notifiers thread-safe Emanuele Giuseppe Esposito
2021-04-21 21:23 ` Vladimir Sementsov-Ogievskiy
2021-04-21 22:17 ` Vladimir Sementsov-Ogievskiy
2021-04-19 8:55 ` [PATCH v2 5/8] block: add a few more notes on locking Emanuele Giuseppe Esposito
2021-05-05 9:53 ` Stefan Hajnoczi
2021-04-19 8:55 ` Emanuele Giuseppe Esposito [this message]
2021-05-05 10:10 ` [PATCH v2 6/8] block: do not acquire AioContext in check_to_replace_node Paolo Bonzini
2021-04-19 8:55 ` [PATCH v2 7/8] block/replication: do not acquire AioContext Emanuele Giuseppe Esposito
2021-05-05 9:57 ` Stefan Hajnoczi
2021-05-05 10:33 ` Paolo Bonzini
2021-04-19 8:55 ` [PATCH v2 8/8] block: do not take AioContext around reopen Emanuele Giuseppe Esposito
2021-04-21 12:24 ` Paolo Bonzini
2021-05-05 10:01 ` Stefan Hajnoczi
2021-04-21 12:25 ` [PATCH v2 0/8] Block layer thread-safety, continued Paolo Bonzini
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=20210419085541.22310-7-eesposit@redhat.com \
--to=eesposit@redhat.com \
--cc=armbru@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@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).