From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com,
Stefan Hajnoczi <stefanha@redhat.com>,
den@openvz.org
Subject: Re: [PATCH 3/4] nbd: make client_close synchronous
Date: Mon, 29 Jun 2020 10:55:06 +0300 [thread overview]
Message-ID: <6f10f2d1-49f3-edff-eff6-0a2f97c07ebc@virtuozzo.com> (raw)
In-Reply-To: <20200625142540.24589-4-vsementsov@virtuozzo.com>
25.06.2020 17:25, Vladimir Sementsov-Ogievskiy wrote:
> client_close doesn't guarantee that client is closed: nbd_trip() keeps
> reference to it. Let's wait for nbd_trip to finish.
>
> Without this fix, the following crash is possible:
>
> - export bitmap through unternal Qemu NBD server
> - connect a client
> - shutdown Qemu
>
> On shutdown nbd_export_close_all is called, but it actually don't wait
> for nbd_trip() to finish and to release its references. So, export is
> not release, and exported bitmap remains busy, and on try to remove the
> bitmap (which is part of bdrv_close()) the assertion fairs:
>
> bdrv_release_dirty_bitmap_locked: Assertion `!bdrv_dirty_bitmap_busy(bitmap)' failed
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> nbd/server.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/nbd/server.c b/nbd/server.c
> index 20754e9ebc..5e27a8d31a 100644
> --- a/nbd/server.c
> +++ b/nbd/server.c
> @@ -1419,6 +1419,8 @@ static void client_close(NBDClient *client, bool negotiated)
> qio_channel_shutdown(client->ioc, QIO_CHANNEL_SHUTDOWN_BOTH,
> NULL);
>
> + AIO_WAIT_WHILE(client->exp->ctx, client->recv_coroutine);
> +
> /* Also tell the client, so that they release their reference. */
> if (client->close_fn) {
> client->close_fn(client, negotiated);
> @@ -2450,6 +2452,7 @@ static coroutine_fn void nbd_trip(void *opaque)
>
> trace_nbd_trip();
> if (client->closing) {
> + client->recv_coroutine = NULL;
> nbd_client_put(client);
> return;
> }
>
I have a doubt, isn't it possible to hang in AIO_WAIT_WHILE() after this patch?
Do we need aio_wait_kick() in the nbd_trip()? Or may be, something like
aio_wait_kick(), but to wake exactly client->exp->ctx aio context?
Also, why in block/io.c we kick the main context, but not bs->aio_context?
--
Best regards,
Vladimir
next prev parent reply other threads:[~2020-06-29 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 14:25 [PATCH 0/4] Fix crash due to NBD export leak Vladimir Sementsov-Ogievskiy
2020-06-25 14:25 ` [PATCH 1/4] iotests: QemuIoInteractive: use qemu_io_args_no_fmt Vladimir Sementsov-Ogievskiy
2020-06-25 19:32 ` Eric Blake
2020-06-25 14:25 ` [PATCH 2/4] iotests.py: QemuIoInteractive: print output on failure Vladimir Sementsov-Ogievskiy
2020-06-25 14:46 ` Eric Blake
2020-06-25 14:25 ` [PATCH 3/4] nbd: make client_close synchronous Vladimir Sementsov-Ogievskiy
2020-06-25 14:48 ` Eric Blake
2020-06-29 7:55 ` Vladimir Sementsov-Ogievskiy [this message]
2020-06-29 13:56 ` Stefan Hajnoczi
2020-07-01 10:19 ` Vladimir Sementsov-Ogievskiy
2020-06-25 14:25 ` [PATCH 4/4] iotests: test shutdown when bitmap is exported through NBD Vladimir Sementsov-Ogievskiy
2020-06-25 15:15 ` [PATCH 0/4] Fix crash due to NBD export leak no-reply
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=6f10f2d1-49f3-edff-eff6-0a2f97c07ebc@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--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).