From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
stefanha@redhat.com, qemu-stable@nongnu.org,
Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>
Subject: Re: [PATCH v2 2/2] iotests: test NBD+TLS+iothread
Date: Mon, 20 May 2024 09:54:52 +0100 [thread overview]
Message-ID: <ZksP3IwzdqzVVg1o@redhat.com> (raw)
In-Reply-To: <iv4tyqsi5bwojgh5hcpr4jfmlw2xvatpgqroxe2dvp27qzbhea@bitj4i5zb5po>
On Fri, May 17, 2024 at 10:08:08PM -0500, Eric Blake wrote:
> Adding a bit of self-review (in case you want to amend this before
> pushing, instead of waiting for me to get back online),
>
> On Fri, May 17, 2024 at 09:50:15PM GMT, Eric Blake wrote:
> > Prevent regressions when using NBD with TLS in the presence of
> > iothreads, adding coverage the fix to qio channels made in the
> > previous patch.
> >
> > CC: qemu-stable@nongnu.org
> > Signed-off-by: Eric Blake <eblake@redhat.com>
> > ---
> > tests/qemu-iotests/tests/nbd-tls-iothread | 170 ++++++++++++++++++
> > tests/qemu-iotests/tests/nbd-tls-iothread.out | 54 ++++++
> > 2 files changed, 224 insertions(+)
> > create mode 100755 tests/qemu-iotests/tests/nbd-tls-iothread
> > create mode 100644 tests/qemu-iotests/tests/nbd-tls-iothread.out
> > +
> > +# pick_unused_port
> > +# Copied from nbdkit/tests/functions.sh.in with compatible 2-clause BSD license
>
> I'm not sure if I have to include the license text verbatim in this
> file, and/or have this function moved to a helper utility file. The
> original source file that I borrowed pick_unused_port from has:
>
> # Copyright Red Hat
I checked most of the relevant history, and this Copyright statement
does indeed appear correct - the code was all written by Richard.
Thus, you could invoke Red Hat's right to re-license and just declare
this copy to be under QEMU's normal GPL license, avoiding the question
of copying the license text.
> > +#
> > +# Picks and returns an "unused" port, setting the global variable
> > +# $port.
> > +#
> > +# This is inherently racy, but we need it because qemu does not currently
> > +# permit NBD+TLS over a Unix domain socket
> > +pick_unused_port ()
> > +{
> > + if ! (ss --version) >/dev/null 2>&1; then
> > + _notrun "ss utility required, skipped this test"
> > + fi
> > +
> > + # Start at a random port to make it less likely that two parallel
> > + # tests will conflict.
> > + port=$(( 50000 + (RANDOM%15000) ))
> > + while ss -ltn | grep -sqE ":$port\b"; do
> > + ((port++))
> > + if [ $port -eq 65000 ]; then port=50000; fi
>
> Also, common.nbd only probes:
> for ((port = 10809; port <= 10909; port++))
> and nbdkit's choice of starting with a random offset is interesting.
Yes, a random offset is a nice idea, massively reducing risk of
clashes through (un)lucky concurrent execution.
> > +echo
> > +echo === Cleaning up ===
> > +echo
> > +
> > +_send_qemu_cmd $h1 '{"execute":"quit"}' ''
> > +_send_qemu_cmd $h2 '{"execute":"quit"}' ''
>
> Since the bug was exposed by this point, I didn't bother to do a clean
> shutdown of the mirror job or NBD export. As is, testing that we shut
> down cleanly despite abandoning a job is probably not a bad idea.
Yeah, perhaps worthwhile, if you can get something that works reliably.
A reliable partial test is better than an unreliable full test, as we'll
just end up killing the latter.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-05-20 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 2:50 [PATCH v2 0/2] Fix NBD+TLS regression in presence of iothread Eric Blake
2024-05-18 2:50 ` [PATCH v2 1/2] qio: Inherit follow_coroutine_ctx across TLS Eric Blake
2024-05-18 2:50 ` [PATCH v2 2/2] iotests: test NBD+TLS+iothread Eric Blake
2024-05-18 3:08 ` Eric Blake
2024-05-20 8:54 ` Daniel P. Berrangé [this message]
2024-05-31 14:36 ` Kevin Wolf
2024-05-31 16:15 ` Eric Blake
2024-05-18 2:56 ` [PATCH v2 0/2] Fix NBD+TLS regression in presence of iothread Eric Blake
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=ZksP3IwzdqzVVg1o@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@yandex-team.ru \
/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).