From: Pavel Machek <pavel@ucw.cz>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
SeongJae Park <sjpark@amazon.com>, Joe Perches <joe@perches.com>,
akpm@linux-foundation.org, apw@canonical.com,
SeongJae Park <sjpark@amazon.de>,
colin.king@canonical.com, sj38.park@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Recommend denylist/allowlist instead of blacklist/whitelist
Date: Mon, 15 Jun 2020 08:12:08 +0200 [thread overview]
Message-ID: <20200615061208.GA31489@amd> (raw)
In-Reply-To: <19ac7f0d-613f-9c8c-8045-e785155fd2e4@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
On Mon 2020-06-15 06:21:43, Jiri Slaby wrote:
> On 14. 06. 20, 23:29, Pavel Machek wrote:
> >> It's not like blacklist / whitelist are even good to begin with, it's
> >> not obvious which is which, you have to learn that black is bad and
> >> white is good.
> >>
> >> Blocklist (or denylist?) and allowlist are actually more descriptive and
> >> less likely to cause confusion.
> >
> > You do not understand how word "blacklist" is used inside the kernel,
> > do you? Do a quick grep.
>
> And now, do the same for "blocklist".
>
> And is "denylist" a proper word? As grep gives zarro results...
>
> It's not that easy to find alternatives. OTOH, admittedly, "blacklist"
> is used improperly in some contexts. Some synonyms fit better.
Well, many of the uses is "list of hardware that needs particular
workaround" or "list of hardware that is broken in some
way"... Neither 'blocklist' nor 'denylist' fit that usage.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-06-15 6:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 6:25 [PATCH v4 0/2] Recommend denylist/allowlist instead of blacklist/whitelist SeongJae Park
2020-06-11 6:25 ` [PATCH v4 1/2] checkpatch: support deprecated terms checking SeongJae Park
2020-07-25 13:02 ` Michał Mirosław
2020-07-25 16:36 ` Joe Perches
2020-07-25 17:29 ` Joe Perches
2020-07-25 23:35 ` SeongJae Park
2020-07-26 4:27 ` Joe Perches
2020-07-26 7:18 ` SeongJae Park
2020-07-26 7:29 ` Joe Perches
2020-07-26 7:45 ` SeongJae Park
2020-07-26 14:50 ` Joe Perches
2020-07-26 15:36 ` SeongJae Park
2020-07-26 16:42 ` Joe Perches
2020-07-26 18:07 ` SeongJae Park
2020-07-26 20:33 ` Michał Mirosław
2020-07-27 6:54 ` SeongJae Park
2020-07-27 20:44 ` Andrew Morton
2020-07-27 20:49 ` Joe Perches
2020-07-28 6:22 ` SeongJae Park
2020-06-11 6:25 ` [PATCH v4 2/2] scripts/deprecated_terms: Recommend denylist/allowlist instead of blacklist/whitelist SeongJae Park
2020-06-11 6:35 ` [PATCH v4 0/2] " Joe Perches
2020-06-11 7:38 ` SeongJae Park
2020-06-11 8:16 ` Jiri Slaby
2020-06-11 8:30 ` SeongJae Park
2020-06-11 8:32 ` Jiri Slaby
2020-06-11 10:43 ` Joe Perches
2020-06-12 6:40 ` SeongJae Park
2020-06-12 7:05 ` Joe Perches
2020-06-12 14:40 ` Michael Ellerman
2020-06-14 21:29 ` Pavel Machek
2020-06-15 4:21 ` Jiri Slaby
2020-06-15 6:12 ` Pavel Machek [this message]
2020-06-15 6:46 ` SeongJae Park
2020-06-15 7:00 ` Joe Perches
2020-06-15 7:39 ` Pavel Machek
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=20200615061208.GA31489@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=colin.king@canonical.com \
--cc=joe@perches.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.com \
--cc=sjpark@amazon.de \
/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).