linux-kernel - Re: [Tech-board-discuss] [Ksummit-discuss] [PATCH v3] CodingStyle: Inclusive Terminology

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1594652811.3750.7.camel@HansenPartnership.com>
Date:   Mon, 13 Jul 2020 08:06:51 -0700
From:   James Bottomley <James.Bottomley@...senPartnership.com>
To:     Takashi Iwai <tiwai@...e.de>,
        Dan Williams <dan.j.williams@...el.com>
Cc:     ksummit-discuss@...ts.linuxfoundation.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        SeongJae Park <sjpark@...zon.de>, linux-kernel@...r.kernel.org,
        tech-board-discuss@...ts.linuxfoundation.org,
        Dave Airlie <airlied@...hat.com>,
        Christian Brauner <christian.brauner@...ntu.com>,
        Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [Tech-board-discuss] [Ksummit-discuss] [PATCH v3] CodingStyle:
 Inclusive Terminology

On Mon, 2020-07-13 at 10:02 +0200, Takashi Iwai wrote:
> On Wed, 08 Jul 2020 20:14:27 +0200,
> Dan Williams wrote:
> > 
> > +Recommended replacements for 'blacklist/whitelist' are:
> > +    'denylist / allowlist'
> > +    'blocklist / passlist'
> 
> I started looking through the tree now and noticed there are lots of
> patterns like "whitelisted" or "blacklisted".  How can the words fit
> for those?  Actually, there are two cases like:
> 
> - Foo is blacklisted
> - Allow to load the non-whitelisted cards
> 
> Currently I'm replacing the former with "Foo is in denylist", but not
> sure about the latter case.  I thought Kees mentioned about this, but
> don't remember the proposal...

Remember these are suggestions for going forwards, not requirements for
changing everything.  We tend to be a community that likes make work
projects because they're easier to do than solving the hard problems,
but since we have over 100k occurrences of the various words in the
kernel, changing them all would cause massive churn and disrupt forward
development, which would cause way more harm than any gain from the
change.

James