From: Fam Zheng <famz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.11] block: Keep strong reference when draining all BDS
Date: Fri, 10 Nov 2017 10:45:57 +0800 [thread overview]
Message-ID: <20171110024557.GB4849@lemon> (raw)
In-Reply-To: <20171109204315.27072-1-mreitz@redhat.com>
On Thu, 11/09 21:43, Max Reitz wrote:
> Draining a BDS may lead to graph modifications, which in turn may result
> in it and other BDS being stripped of their current references. If
> bdrv_drain_all_begin() and bdrv_drain_all_end() do not keep strong
> references themselves, the BDS they are trying to drain (or undrain) may
> disappear right under their feet -- or, more specifically, under the
> feet of BDRV_POLL_WHILE() in bdrv_drain_recurse().
>
> This fixes an occasional hang of iotest 194.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> block/io.c | 47 ++++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 44 insertions(+), 3 deletions(-)
>
> diff --git a/block/io.c b/block/io.c
> index 3d5ef2cabe..a0a2833e8e 100644
> --- a/block/io.c
> +++ b/block/io.c
> @@ -340,7 +340,10 @@ void bdrv_drain_all_begin(void)
> bool waited = true;
> BlockDriverState *bs;
> BdrvNextIterator it;
> - GSList *aio_ctxs = NULL, *ctx;
> + GSList *aio_ctxs = NULL, *ctx, *bs_list = NULL, *bs_list_entry;
> +
> + /* Must be called from the main loop */
> + assert(qemu_get_current_aio_context() == qemu_get_aio_context());
>
> block_job_pause_all();
>
> @@ -355,6 +358,12 @@ void bdrv_drain_all_begin(void)
> if (!g_slist_find(aio_ctxs, aio_context)) {
> aio_ctxs = g_slist_prepend(aio_ctxs, aio_context);
> }
> +
> + /* Keep a strong reference to all root BDS and copy them into
> + * an own list because draining them may lead to graph
> + * modifications. */
> + bdrv_ref(bs);
> + bs_list = g_slist_prepend(bs_list, bs);
> }
>
> /* Note that completion of an asynchronous I/O operation can trigger any
> @@ -370,7 +379,11 @@ void bdrv_drain_all_begin(void)
> AioContext *aio_context = ctx->data;
>
> aio_context_acquire(aio_context);
> - for (bs = bdrv_first(&it); bs; bs = bdrv_next(&it)) {
> + for (bs_list_entry = bs_list; bs_list_entry;
> + bs_list_entry = bs_list_entry->next)
> + {
> + bs = bs_list_entry->data;
> +
> if (aio_context == bdrv_get_aio_context(bs)) {
> waited |= bdrv_drain_recurse(bs, true);
> }
> @@ -379,24 +392,52 @@ void bdrv_drain_all_begin(void)
> }
> }
>
> + for (bs_list_entry = bs_list; bs_list_entry;
> + bs_list_entry = bs_list_entry->next)
> + {
> + bdrv_unref(bs_list_entry->data);
> + }
> +
> g_slist_free(aio_ctxs);
> + g_slist_free(bs_list);
> }
>
> void bdrv_drain_all_end(void)
> {
> BlockDriverState *bs;
> BdrvNextIterator it;
> + GSList *bs_list = NULL, *bs_list_entry;
> +
> + /* Must be called from the main loop */
> + assert(qemu_get_current_aio_context() == qemu_get_aio_context());
>
> + /* Keep a strong reference to all root BDS and copy them into an
> + * own list because draining them may lead to graph modifications.
> + */
> for (bs = bdrv_first(&it); bs; bs = bdrv_next(&it)) {
> - AioContext *aio_context = bdrv_get_aio_context(bs);
> + bdrv_ref(bs);
> + bs_list = g_slist_prepend(bs_list, bs);
> + }
> +
> + for (bs_list_entry = bs_list; bs_list_entry;
> + bs_list_entry = bs_list_entry->next)
> + {
> + AioContext *aio_context;
> +
> + bs = bs_list_entry->data;
> + aio_context = bdrv_get_aio_context(bs);
>
> aio_context_acquire(aio_context);
> aio_enable_external(aio_context);
> bdrv_parent_drained_end(bs);
> bdrv_drain_recurse(bs, false);
> aio_context_release(aio_context);
> +
> + bdrv_unref(bs);
> }
>
> + g_slist_free(bs_list);
> +
> block_job_resume_all();
> }
>
> --
> 2.13.6
>
>
It is better to put the references into BdrvNextIterator and introduce
bdrv_next_iterator_destroy() to free them? You'll need to touch all callers
because it is not C++, but it secures all of rest, which seems vulnerable in the
same pattern, for example the aio_poll() in iothread_stop_all().
Fam
next prev parent reply other threads:[~2017-11-10 2:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 20:43 [Qemu-devel] [PATCH for-2.11] block: Keep strong reference when draining all BDS Max Reitz
2017-11-09 21:02 ` Eric Blake
2017-11-10 2:45 ` Fam Zheng [this message]
2017-11-10 13:17 ` Kevin Wolf
2017-11-10 13:32 ` Fam Zheng
2017-11-10 15:23 ` Max Reitz
2017-11-10 15:31 ` Fam Zheng
2017-11-10 16:05 ` Kevin Wolf
2017-11-10 16:13 ` Max Reitz
2017-11-10 16:22 ` Kevin Wolf
2017-11-10 16:43 ` Max Reitz
2017-11-10 9:19 ` Stefan Hajnoczi
2017-11-10 15:26 ` 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=20171110024557.GB4849@lemon \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).