Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1430578ybt; Sun, 14 Jun 2020 23:14:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyKrvs/o92gJaKl/hhFFah2920+FmiO1BhZx1J7M+QID1kYWDRyAYftWJA6kYSoGo7SQJrq X-Received: by 2002:a17:906:cd03:: with SMTP id oz3mr25321461ejb.391.1592201673519; Sun, 14 Jun 2020 23:14:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592201673; cv=none; d=google.com; s=arc-20160816; b=IZiN/3QRWc0PMio9rGxf1rBkoass0zj0sCUd6Id+BJ97LT6p/xo48bxzH1ELKiqroy guEbbCVNwtDVkWdiheb6koquKTB50U93q35Xorpfq2X54ximfQt4YJ3zGPFKTugGOQaw WB7XJHw7X5fh8gM+P8JAplfAV4lrKfXq5NSaNEPxlIxE8Q4HY4q2OVCyXmMBZ49WtvwF ar9Ydl2qnNQuQaHSyU45T6FQyjrx7jOKQYZ0YzArujME/Xo55/eVeWqfC7WTNDhRJcBg eW2vmfkuAkLVjtJzS98YHJ1jl3K83HpiD4QJfGH4CrOeY9KNYQFwdYhj0BXg5vt9H/cH JktA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=+9Wkggeae+OGWWcTbsPfsEfCWFV9fkLAWGbbh9dUN4k=; b=weQlbctnF1zAxHbQR7WMcPBWK1YOf9v9OT3tR17yzvxjB3Jyk7u/vUWPEdTQR73x+p KgX93MCympnKkMuOfOjPfvX50y8+bKIh+YGnKlF3RtB9eBI3OBEE4XBL7g8pekHFUGRn xZM3gs07m54FuLr/H8Jlb0CXCfgmYuL2ulomBcoIUfA9k3WBymdW9XHDFv4e4fIyiwWZ 0R3BeBXG2Yyl5fejcxORKynYaiGEmulsPNrbH6XgcKV8hsG3vjmGKRvTs9o3j0wA4KQF 5tmC9XJy3fM9jb5S6qfugHNaecQRy/kTXZU3hlJNlmC57D/h6Kgei3KNa/tVZp2sTp5B +dKQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id eb10si9890250edb.410.2020.06.14.23.14.11; Sun, 14 Jun 2020 23:14:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728320AbgFOGMK (ORCPT + 99 others); Mon, 15 Jun 2020 02:12:10 -0400 Received: from jabberwock.ucw.cz ([46.255.230.98]:56664 "EHLO jabberwock.ucw.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728163AbgFOGMK (ORCPT ); Mon, 15 Jun 2020 02:12:10 -0400 Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id 863431C0BD2; Mon, 15 Jun 2020 08:12:08 +0200 (CEST) Date: Mon, 15 Jun 2020 08:12:08 +0200 From: Pavel Machek To: Jiri Slaby Cc: Michael Ellerman , SeongJae Park , Joe Perches , akpm@linux-foundation.org, apw@canonical.com, SeongJae Park , 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 Message-ID: <20200615061208.GA31489@amd> References: <20200611073804.10225-1-sjpark@amazon.com> <38ac91ab-ced3-8a4f-b825-4503fdcddeb8@suse.cz> <877dwcfitg.fsf@mpe.ellerman.id.au> <20200614212911.GB24529@amd> <19ac7f0d-613f-9c8c-8045-e785155fd2e4@suse.cz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline In-Reply-To: <19ac7f0d-613f-9c8c-8045-e785155fd2e4@suse.cz> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 a= nd > >> less likely to cause confusion. > >=20 > > You do not understand how word "blacklist" is used inside the kernel, > > do you? Do a quick grep. >=20 > And now, do the same for "blocklist". >=20 > And is "denylist" a proper word? As grep gives zarro results... >=20 > 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 --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAl7nETgACgkQMOfwapXb+vLAFQCfaV+RvcVMWAndDcGFxqr3rLup STcAn0J4kZos/bvffljlxvc2aHLwdzy3 =1ptF -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD--