From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Hanna Reitz <hreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2] tests/qemu-iotests/149: Use more inclusive language in this test
Date: Mon, 13 Nov 2023 17:00:25 +0000 [thread overview]
Message-ID: <ZVJWKdDYSeeEthmD@redhat.com> (raw)
In-Reply-To: <20231113165642.62012-1-thuth@redhat.com>
On Mon, Nov 13, 2023 at 05:56:42PM +0100, Thomas Huth wrote:
> Let's use 'unsupported_configs' and 'tested_configs' here instead
> of non-inclusive words.
>
> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v2: Use different wordings (suggested by Paolo)
>
> tests/qemu-iotests/149 | 16 +++++++++-------
> tests/qemu-iotests/149.out | 8 ++++----
> 2 files changed, 13 insertions(+), 11 deletions(-)
>
> diff --git a/tests/qemu-iotests/149 b/tests/qemu-iotests/149
> index 2ae318f16f..2a8bb5787f 100755
> --- a/tests/qemu-iotests/149
> +++ b/tests/qemu-iotests/149
> @@ -518,7 +518,7 @@ configs = [
>
> ]
>
> -blacklist = [
> +unsupported_configs = [
> # We don't have a cast-6 cipher impl for QEMU yet
> "cast6-256-xts-plain64-sha1",
> "cast6-128-xts-plain64-sha1",
> @@ -528,17 +528,19 @@ blacklist = [
> "twofish-192-xts-plain64-sha1",
> ]
>
> -whitelist = []
> +# Optionally test only the configurations in the LUKS_CONFIG
> +# environment variable
> +tested_configs = None
> if "LUKS_CONFIG" in os.environ:
> - whitelist = os.environ["LUKS_CONFIG"].split(",")
> + tested_configs = os.environ["LUKS_CONFIG"].split(",")
>
> for config in configs:
> - if config.name in blacklist:
> - iotests.log("Skipping %s in blacklist" % config.name)
> + if config.name in unsupported_configs:
> + iotests.log("Skipping %s (cipher not supported)" % config.name)
s/cipher/config/ - this is about more than just ciphers - it is the
combination of algorithms (cipher, hash, ivgen).
> continue
>
> - if len(whitelist) > 0 and config.name not in whitelist:
> - iotests.log("Skipping %s not in whitelist" % config.name)
> + if tested_configs is not None and config.name not in tested_configs:
> + iotests.log("Skipping %s (not in LUKS_CONFIG)" % config.name)
This is essentially at the demand of the person invoking it, so I'd
say
s/not in LUKS_CONFIG/by user request/
> continue
>
> test_once(config, qemu_img=False)
> diff --git a/tests/qemu-iotests/149.out b/tests/qemu-iotests/149.out
> index 2cc5b82f7c..3c731bdf95 100644
> --- a/tests/qemu-iotests/149.out
> +++ b/tests/qemu-iotests/149.out
> @@ -470,7 +470,7 @@ sudo cryptsetup -q -v luksClose qiotest-145-cast5-128-cbc-plain64-sha1
> # Delete image
> unlink TEST_DIR/luks-cast5-128-cbc-plain64-sha1.img
>
> -Skipping cast6-256-xts-plain64-sha1 in blacklist
> +Skipping cast6-256-xts-plain64-sha1 (cipher not supported)
> # ================= dm-crypt aes-256-cbc-plain-sha1 =================
> # Create image
> truncate TEST_DIR/luks-aes-256-cbc-plain-sha1.img --size 4194304MB
> @@ -1297,7 +1297,7 @@ sudo cryptsetup -q -v luksClose qiotest-145-twofish-128-xts-plain64-sha1
> # Delete image
> unlink TEST_DIR/luks-twofish-128-xts-plain64-sha1.img
>
> -Skipping twofish-192-xts-plain64-sha1 in blacklist
> +Skipping twofish-192-xts-plain64-sha1 (cipher not supported)
> # ================= dm-crypt serpent-128-xts-plain64-sha1 =================
> # Create image
> truncate TEST_DIR/luks-serpent-128-xts-plain64-sha1.img --size 4194304MB
> @@ -1534,8 +1534,8 @@ sudo cryptsetup -q -v luksClose qiotest-145-serpent-192-xts-plain64-sha1
> # Delete image
> unlink TEST_DIR/luks-serpent-192-xts-plain64-sha1.img
>
> -Skipping cast6-128-xts-plain64-sha1 in blacklist
> -Skipping cast6-192-xts-plain64-sha1 in blacklist
> +Skipping cast6-128-xts-plain64-sha1 (cipher not supported)
> +Skipping cast6-192-xts-plain64-sha1 (cipher not supported)
> # ================= dm-crypt aes-256-xts-plain64-sha224 =================
> # Create image
> truncate TEST_DIR/luks-aes-256-xts-plain64-sha224.img --size 4194304MB
> --
> 2.41.0
>
>
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 :|
prev parent reply other threads:[~2023-11-13 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 16:56 [PATCH v2] tests/qemu-iotests/149: Use more inclusive language in this test Thomas Huth
2023-11-13 17:00 ` Daniel P. Berrangé [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=ZVJWKdDYSeeEthmD@redhat.com \
--to=berrange@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.