[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200615061208.GA31489@amd>
Date: Mon, 15 Jun 2020 08:12:08 +0200
From: Pavel Machek <pavel@....cz>
To: Jiri Slaby <jslaby@...e.cz>
Cc: Michael Ellerman <mpe@...erman.id.au>,
SeongJae Park <sjpark@...zon.com>,
Joe Perches <joe@...ches.com>, akpm@...ux-foundation.org,
apw@...onical.com, SeongJae Park <sjpark@...zon.de>,
colin.king@...onical.com, sj38.park@...il.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/2] Recommend denylist/allowlist instead of
blacklist/whitelist
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
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists