From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Eduardo Otubo" <otubo@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-block@nongnu.org, "Michael Roth" <michael.roth@amd.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [PATCH 10/12] tests/qemu-iotests: Replace the words 'blacklist/whitelist'
Date: Wed, 3 Feb 2021 15:50:23 +0000 [thread overview]
Message-ID: <20210203155023.GV300990@redhat.com> (raw)
In-Reply-To: <20210203154133.GD5507@merkur.fritz.box>
On Wed, Feb 03, 2021 at 04:41:33PM +0100, Kevin Wolf wrote:
> Am 03.02.2021 um 11:28 hat Daniel P. Berrangé geschrieben:
> > On Tue, Feb 02, 2021 at 09:58:22PM +0100, Philippe Mathieu-Daudé wrote:
> > > Follow the inclusive terminology from the "Conscious Language in your
> > > Open Source Projects" guidelines [*] and replace the words "blacklist"
> > > and "whitelist" appropriately.
>
> We're not doing access control here, so allowlist/denylist are not the
> appropriate words to use here.
>
> > > [*] https://github.com/conscious-lang/conscious-lang-docs/blob/main/faq.md
> > >
> > > Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> > > ---
> > > tests/qemu-iotests/149 | 14 +++++++-------
> > > tests/qemu-iotests/149.out | 8 ++++----
> > > 2 files changed, 11 insertions(+), 11 deletions(-)
> > >
> > > diff --git a/tests/qemu-iotests/149 b/tests/qemu-iotests/149
> > > index 328fd05a4c9..b1d3f5fad67 100755
> > > --- a/tests/qemu-iotests/149
> > > +++ b/tests/qemu-iotests/149
> > > @@ -500,7 +500,7 @@ configs = [
> > >
> > > ]
> > >
> > > -blacklist = [
> > > +denylist = [
> > > # We don't have a cast-6 cipher impl for QEMU yet
> > > "cast6-256-xts-plain64-sha1",
> > > "cast6-128-xts-plain64-sha1",
> > > @@ -510,17 +510,17 @@ blacklist = [
> > > "twofish-192-xts-plain64-sha1",
> > > ]
> >
> > "skiplist" better describes the purpose of this.
>
> That it's a list is very obvious from the code and doesn't tell anything
> about the content. How about skip_configs?
Sure
> > >
> > > -whitelist = []
> > > +allowlist = []
> > > if "LUKS_CONFIG" in os.environ:
> > > - whitelist = os.environ["LUKS_CONFIG"].split(",")
> > > + allowlist = os.environ["LUKS_CONFIG"].split(",")
> >
> > And "filterlist"
>
> test_configs? configs_to_test?
The list of configs to test is built up by the code. This
env variable is just a hack to let me filter the configs
for debugging. Just "filter_configs" is ok.
>
> > >
> > > for config in configs:
> > > - if config.name in blacklist:
> > > - iotests.log("Skipping %s in blacklist" % config.name)
> > > + if config.name in denylist:
> > > + iotests.log("Skipping %s in denylist" % config.name)
> > > continue
> > >
> > > - if len(whitelist) > 0 and config.name not in whitelist:
> > > - iotests.log("Skipping %s not in whitelist" % config.name)
> > > + if len(allowlist) > 0 and config.name not in allowlist:
> > > + iotests.log("Skipping %s not in allowlist" % config.name)
> > > continue
>
> The messages need to be updates accordingly, of course.
>
> Kevin
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:[~2021-02-03 15:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 20:58 [PATCH 00/12] misc: Replace the words 'blacklist/whitelist' Philippe Mathieu-Daudé
2021-02-02 20:58 ` [PATCH 01/12] ui: Replace the word 'whitelist' Philippe Mathieu-Daudé
2021-02-03 9:43 ` Gerd Hoffmann
2021-02-03 10:04 ` Daniel P. Berrangé
2021-02-04 9:04 ` Philippe Mathieu-Daudé
2021-02-02 20:58 ` [PATCH 02/12] qga: Rename config key 'blacklist' as 'denylist' Philippe Mathieu-Daudé
2021-02-03 10:17 ` Daniel P. Berrangé
2021-02-04 9:45 ` Michal Suchánek
2021-02-04 12:29 ` Michal Suchánek
2021-02-02 20:58 ` [PATCH 03/12] qga: Replace '--blacklist' command line option by '--denylist' Philippe Mathieu-Daudé
2021-02-03 10:09 ` Daniel P. Berrangé
2021-02-03 12:45 ` BALATON Zoltan
2021-02-03 15:47 ` Kevin Wolf
2021-02-03 16:02 ` Michael Roth
2022-07-18 16:17 ` Thomas Huth
2021-02-02 20:58 ` [PATCH 04/12] qga: Replace the word 'blacklist' Philippe Mathieu-Daudé
2021-02-03 10:10 ` Daniel P. Berrangé
2021-02-02 20:58 ` [PATCH 05/12] tools/virtiofsd: Replace the word 'whitelist' Philippe Mathieu-Daudé
2021-02-03 9:08 ` Dr. David Alan Gilbert
2021-02-03 10:11 ` Daniel P. Berrangé
2021-02-02 20:58 ` [PATCH 06/12] scripts/tracetool: " Philippe Mathieu-Daudé
2021-02-03 10:12 ` Daniel P. Berrangé
2021-02-03 14:31 ` Stefan Hajnoczi
2021-02-02 20:58 ` [PATCH 07/12] scripts/device-crash-test: " Philippe Mathieu-Daudé
2021-02-03 9:14 ` Philippe Mathieu-Daudé
2021-02-03 10:14 ` Daniel P. Berrangé
2021-02-02 20:58 ` [PATCH 08/12] seccomp: Replace the word 'blacklist' Philippe Mathieu-Daudé
2021-02-03 10:15 ` Daniel P. Berrangé
2021-02-03 10:41 ` Eduardo Otubo
2021-02-02 20:58 ` [PATCH 09/12] qemu-options: " Philippe Mathieu-Daudé
2021-02-03 10:25 ` Daniel P. Berrangé
2021-02-04 9:09 ` Philippe Mathieu-Daudé
2021-02-02 20:58 ` [PATCH 10/12] tests/qemu-iotests: Replace the words 'blacklist/whitelist' Philippe Mathieu-Daudé
2021-02-03 10:28 ` Daniel P. Berrangé
2021-02-03 15:41 ` Kevin Wolf
2021-02-03 15:50 ` Daniel P. Berrangé [this message]
2021-02-02 20:58 ` [PATCH 11/12] tests/fp/fp-test: Replace the word 'blacklist' Philippe Mathieu-Daudé
2021-02-03 9:20 ` Alex Bennée
2021-02-03 10:29 ` Daniel P. Berrangé
2021-02-02 20:58 ` [PATCH 12/12] hw/vfio/pci-quirks: " Philippe Mathieu-Daudé
2021-02-02 22:13 ` Alex Williamson
2021-02-03 10:30 ` Daniel P. Berrangé
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=20210203155023.GV300990@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=aurelien@aurel32.net \
--cc=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=michael.roth@amd.com \
--cc=mreitz@redhat.com \
--cc=otubo@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@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).