From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, armbru@redhat.com, hreitz@redhat.com,
kwolf@redhat.com, eblake@redhat.com
Subject: Re: [PATCH v4 0/7] nbd reconnect on open
Date: Tue, 21 Dec 2021 17:17:40 +0300 [thread overview]
Message-ID: <d60a7c8c-c134-0b5d-bcae-1107ea3cc3fa@virtuozzo.com> (raw)
In-Reply-To: <20211213153240.480103-1-vsementsov@virtuozzo.com>
13.12.2021 18:32, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> The functionality is reviewed, python testing part is not.
>
> I've dropped the patch "qapi: make blockdev-add a coroutine command":
> it's optional, I don't want to slow down the whole series because of it.
>
> v4:
> 01-03: wording, add Eric's r-b
> others: small changes, never had an r-b
>
> Vladimir Sementsov-Ogievskiy (7):
> nbd: allow reconnect on open, with corresponding new options
> nbd/client-connection: nbd_co_establish_connection(): return real
> error
> nbd/client-connection: improve error message of cancelled attempt
> iotests.py: add qemu_tool_popen()
> For qemu_io* functions support --image-opts argument, which conflicts
> with -f argument from qemu_io_args.
> Add qemu-io Popen constructor wrapper. To be used in the following new
> test commit.
> iotests: add nbd-reconnect-on-open test
>
> qapi/block-core.json | 9 ++-
> block/nbd.c | 45 +++++++++++-
> nbd/client-connection.c | 59 ++++++++++-----
> tests/qemu-iotests/iotests.py | 36 ++++++----
> .../qemu-iotests/tests/nbd-reconnect-on-open | 71 +++++++++++++++++++
> .../tests/nbd-reconnect-on-open.out | 11 +++
> 6 files changed, 199 insertions(+), 32 deletions(-)
> create mode 100755 tests/qemu-iotests/tests/nbd-reconnect-on-open
> create mode 100644 tests/qemu-iotests/tests/nbd-reconnect-on-open.out
>
Thanks for reviewing!
I do s/6.2/7.0/ fix to patch 1, restore subjects of patches 5,6 (which were somehow lost in transition v3->v4) and apply the series to my nbd branch.
--
Best regards,
Vladimir
prev parent reply other threads:[~2021-12-21 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 15:32 [PATCH v4 0/7] nbd reconnect on open Vladimir Sementsov-Ogievskiy
2021-12-13 15:32 ` [PATCH v4 1/7] nbd: allow reconnect on open, with corresponding new options Vladimir Sementsov-Ogievskiy
2021-12-13 20:50 ` Eric Blake
2021-12-13 15:32 ` [PATCH v4 2/7] nbd/client-connection: nbd_co_establish_connection(): return real error Vladimir Sementsov-Ogievskiy
2021-12-13 15:32 ` [PATCH v4 3/7] nbd/client-connection: improve error message of cancelled attempt Vladimir Sementsov-Ogievskiy
2021-12-13 15:32 ` [PATCH v4 4/7] iotests.py: add qemu_tool_popen() Vladimir Sementsov-Ogievskiy
2021-12-20 11:45 ` Nikta Lapshin
2021-12-13 15:32 ` [PATCH v4 5/7] For qemu_io* functions support --image-opts argument, which conflicts with -f argument from qemu_io_args Vladimir Sementsov-Ogievskiy
2021-12-20 11:46 ` Nikta Lapshin
2021-12-13 15:32 ` [PATCH v4 6/7] Add qemu-io Popen constructor wrapper. To be used in the following new test commit Vladimir Sementsov-Ogievskiy
2021-12-20 11:47 ` Nikta Lapshin
2021-12-13 15:32 ` [PATCH v4 7/7] iotests: add nbd-reconnect-on-open test Vladimir Sementsov-Ogievskiy
2021-12-20 11:48 ` Nikta Lapshin
2021-12-21 14:17 ` Vladimir Sementsov-Ogievskiy [this message]
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=d60a7c8c-c134-0b5d-bcae-1107ea3cc3fa@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@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).