07.05.20

Systems Can Crash and People Can Die by Changing Language (Even in Parameter and Function Space) to Appease Activists

Posted in Free/Libre Software, GNU/Linux, Kernel at 7:25 am by Dr. Roy Schestowitz

There are also purely practical considerations to be taken into account (and the worst culprits are Windows people)

Microsoft Apologizes, Removes 'Big Boobs' String From Linux Code
Older: Microsoft Apologizes, Removes ‘Big Boobs’ String From Linux Code

Summary: It seems clear that Intel takes the lead in trying to change Linux not in technical means but purely social means; even when (and where) that can compromise the robustness of the kernel (Intel is nowadays known for profoundly defective chips with back doors)

MANNERS are a good thing. Being polite is also always preferable. It might not always be possible, but it is preferable.

“The company which commits so many crimes claims to be a source for good, a voice for ethics.”It’s difficult to forget how people who wrote bad code complained about Torvalds. Eventually he was even ‘removed’ from the project — his own ‘baby’ — for about a month. Intel played a big role in that. As we’ve noted before, Intel keeps coming back. The company which commits so many crimes claims to be a source for good, a voice for ethics. Welcome to the brave new world… white is black, black is white.

It’s no secret that changing words inside code (not literature) can complicate things, break things, become an expensive development venture and even cause systems to fail/break down (unexpectedly). Some mission-critical systems (aviation, hospitals and disaster recovery) are also impacted. It’s an endless adventure; you’ll never please everyone. Just taking the latest article from Phoronix, it says “A.k.a. Spectre, Meltdown, etc.” and we all know what “Spectre” is to “Master” and what “Meltdown” is to people with mental health issues [1].

Should we remove all mentions of these terms as well? Where does it end? By the way, slavery is not a thing of the past but a thing of the present. Many Africans are still enslaved by fellow Africans and many are sold as slaves. Deleting particular words may make it harder to explain the problem, which is still ongoing (see the UN’s Web site).

“Remember how Intel viciously attacked children’s education in Africa.”The other morning coverage in Phoronix says there’s an effort wherein “Linux Kernel [is] Preparing New Guidelines For Using Inclusive Terminology” (included in circulation are two people from the Linux Foundation, one from Intel, another from Facebook and lastly one from Google). To quote Michael Larabel: “The exception being granted though is where changing the terminology could potentially break the user-space ABI given the kernel’s longstanding guarantees on not breaking that interface.” (Many comments on this, 54 as of this morning, with more noteworthy comments — 21 of them so far — in CNX Software under “New Tech Vocabulary for 2020 Could Break Software Compatibility”)

Not many have mentioned the aspect of debugging being necessary (if not rewriting of software units, followed by a lot of testing). It can also harm backward compatibility and thus increase electronic waste, harming the environment. We all know that a lot of electronic waste (basically Western trash) is being shipped to Africa, outsourcing the pollution to ‘lesser’ races, right? So much for justice…

Looking at the original, however, and bearing in mind what some Intel employees already did to sanitise Linux (see “New Patch Replaces F-Words in Linux Kernel Code with “Hug”) while Intel became speech police in the whole project, this is what we have from Intel’s Dan Williams ([PATCH] CodingStyle: Inclusive Terminology):

Recent events have prompted a Linux position statement on inclusive
terminology. Given that Linux maintains a coding-style and its own
idiomatic set of terminology here is a proposal to answer the call to
replace non-inclusive terminology.

Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Kees Cook <keescook@chromium.org>
Signed-off-by: Chris Mason <clm@fb.clm>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>

Documentation/process/coding-style.rst | 12 ++++
Documentation/process/inclusive-terminology.rst | 64 +++++++++++++++++++++++
Documentation/process/index.rst | 1
3 files changed, 77 insertions(+)
create mode 100644 Documentation/process/inclusive-terminology.rst

diff –git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
index 2657a55c6f12..4b15ab671089 100644
— a/Documentation/process/coding-style.rst
+++ b/Documentation/process/coding-style.rst
@@ -319,6 +319,18 @@ If you are afraid to mix up your local variable names, you have another
problem, which is called the function-growth-hormone-imbalance syndrome.
See chapter 6 (Functions).

+For symbol names, avoid introducing new usage of the words ‘slave’ and
+’blacklist’. Recommended replacements for ‘slave’ are: ‘secondary’,
+’subordinate’, ‘replica’, ‘responder’, ‘follower’, ‘proxy’, or
+’performer’. Recommended replacements for blacklist are: ‘blocklist’ or
+’denylist’.
+
+Exceptions for introducing new usage is to maintain a userspace ABI, or
+when updating code for an existing (as of 2020) hardware or protocol
+specification that mandates those terms. For new specifications consider
+translating specification usage of the terminology to the kernel coding
+standard where possible. See :ref:`process/inclusive-terminology.rst
+<inclusiveterminology>` for details.

5) Typedefs
———–
diff –git a/Documentation/process/inclusive-terminology.rst b/Documentation/process/inclusive-terminology.rst
new file mode 100644
index 000000000000..a8eb26690eb4
— /dev/null
+++ b/Documentation/process/inclusive-terminology.rst
@@ -0,0 +1,64 @@
+.. _inclusiveterminology:
+
+Linux kernel inclusive terminology
+==================================
+
+The Linux kernel is a global software project, and in 2020 there was a
+global reckoning on race relations that caused many organizations to
+re-evaluate their policies and practices relative to the inclusion of
+people of African descent. This document describes why the ‘Naming’
+section in :ref:`process/coding-style.rst <codingstyle>` recommends
+avoiding usage of ‘slave’ and ‘blacklist’ in new additions to the Linux
+kernel.
+
+On the triviality of replacing words
+====================================
+
+The African slave trade was a brutal system of human misery deployed at
+global scale. Some word choice decisions in a modern software project
+does next to nothing to compensate for that legacy. So why put any
+effort into something so trivial in comparison? Because the goal is not
+to repair, or erase the past. The goal is to maximize availability and
+efficiency of the global developer community to participate in the Linux
+kernel development process.
+
+Word choice and developer efficiency
+====================================
+
+Why does any software project go through the trouble of developing a
+document like :ref:`process/coding-style.rst <codingstyle>`? It does so
+because a common coding style maximizes the efficiency of both
+maintainers and developers. Developers learn common design patterns and
+idiomatic expressions while maintainers can spot deviations from those
+norms. Even non-compliant whitespace is considered a leading indicator
+to deeper problems in a patchset. Coding style violations are known to
+take a maintainer “out of the zone” of reviewing code. Maintainers are
+also sensitive to word choice across specifications and often choose to
+deploy Linux terminology to replace non-idiomatic word-choice in a
+specification.
+
+Non-inclusive terminology has that same distracting effect which is why
+it is a style issue for Linux, it injures developer efficiency.
+
+Of course it is around this point someone jumps in with an etymological
+argument about why people should not be offended. Etymological arguments
+do not scale. The scope and pace of Linux to reach new developers
+exceeds the ability of historical terminology defenders to describe “no,
+not that connotation”. The revelation of 2020 was that black voices were
+heard on a global scale and the Linux kernel project has done its small
+part to answer that call as it wants black voices, among all voices, in
+its developer community.
+
+Really, ‘blacklist’ too?
+========================
+
+While ‘slave’ has a direct connection to human suffering the etymology
+of ‘blacklist’ is devoid of a historical racial connection. However, one
+thought exercise is to consider replacing ‘blacklist/whitelist’ with
+’redlist/greenlist’. Realize that the replacement only makes sense if
+you have been socialized with the concepts that ‘red/green’ implies
+’stop/go’. Colors to represent a policy requires an indirection. The
+socialization of ‘black/white’ to have the connotation of
+’impermissible/permissible’ does not support inclusion.
+
+Inclusion == global developer community efficiency.
diff –git a/Documentation/process/index.rst b/Documentation/process/index.rst
index f07c9250c3ac..ed861f6f8d25 100644
— a/Documentation/process/index.rst
+++ b/Documentation/process/index.rst
@@ -27,6 +27,7 @@ Below are the essential guides that every developer should read.
submitting-patches
programming-language
coding-style
+ inclusive-terminology
maintainer-pgp-guide
email-clients
kernel-enforcement-statement

Notice the mention of ‘redlist/greenlist’; we've already mentioned why that too can be interpreted as "racist". It’s a never-ending game and nuance brought to such ‘overdrive’ (oversensitivity) means no good will come out of it. Richard Stallman has just remarked on the word “whitening” being phased out (even when it literally means just that, e.g. dental products).

“Intel is using black people (exploiting legitimate race grievances) to socially-engineer and interject disruption into a project it cannot control because of the GPL.”There aren’t many African contributors in Linux not because of the language but because African nations are poor and lack access to particular computing resources (sometimes Internet connections as well). Maybe focus on those latter issues before obsessing over the colour of some alert or a rule? Companies like Intel would rather have us speaking/bickering about race issues than class/wealth issues. Remember how Intel viciously attacked children’s education in Africa. All in the name of profit! Intel is using black people (exploiting legitimate race grievances) to socially-engineer and interject disruption into a project it cannot control because of the GPL.

Related/contextual items from the news:

  1. New readfile() System Call Under Review For Reading Small~Medium Files Faster

    Besides readfile() being simpler, the other intended use-case is for helping in performance due to less system calls. Greg does note that utilizing readfile should help performance, especially due to “syscall overheads go up over time due to various CPU bugs being addressed.” A.k.a. Spectre, Meltdown, etc.

    The readfile system call review is in this kernel thread. Hopefully it will be reviewed punctually and well to possibly make it into the Linux 5.9 cycle next month.

  2. Linux Kernel Preparing New Guidelines For Using Inclusive Terminology

    The new inclusive terminology documentation applies to new code being contributed to the Linux kernel but ultimately in hopes of replacing existing code with words deemed not inclusive. The exception being granted though is where changing the terminology could potentially break the user-space ABI given the kernel’s longstanding guarantees on not breaking that interface.

    These new guidelines for Linux kernel developers call for initially avoiding words including “slave” and “blacklist” to instead use words like subordinate, replica, follower, performer, blocklist, or denylist.

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

This post is also available in Gemini over at:

gemini://gemini.techrights.org/2020/07/05/give-finger-they-want-the-hand/

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New


  1. [Meme] Bundestagate Series Spoiler

    The chain of command/s at the EPO typically leads to major tragedy



  2. Breaking News: Campinos to Appear Before the Legals Affairs Committee of the European Parliament on Monday 12 April

    "Some MEPs have been briefed about ongoing governance deficits at the EPO, in particular the lack of GDPR compliance and the sell-out of "digital sovereignty" to Microsoft, but it remains to be seen whether or not they will dare to bring these issues up during the hearing."



  3. Pro-FSF Petition (“An Open Letter in Support of Richard Matthew Stallman Being Reinstated by the Free Software Foundation”) Tops 6,200 Signatures

    Monopolies and their media, along with their NGOs, have spoken and incited based on falsehoods; people now respond so the hate letter has a real crisis



  4. Links 10/4/2021: osbuild 28, KDE Frameworks 5.81.0

    Links for the day



  5. EPOLeaks on Misleading the Bundestag -- Part 12: A Worthy Successor to His Mentor?

    We examine the role of Christoph Ernst in EPO management, both in the Benoît Battistelli era and the António Campinos era (plenty to hide)



  6. USPTO for Monopolies, Keeping GNU/Linux in the Dark

    Growing evidence of gross discrimination against GNU/Linux (or Free software, even BSD/UNIX) users at the USPTO is too hard to ignore; some people out there challenge the Office over this travesty



  7. Accessibility and Availability First

    To make Techrights more widely accessible and more difficult to block/censor we've been making further changes, including self-hosting where possible



  8. Self-Hosting Videos With Free Formats and Animated Previews, Watermarks/Logos and Translucency

    We examine the power of video editing with ffmpeg, chained with command-line scripting and HTML5 features



  9. Links 10/4/2021: Linux on M1, Wine 6.6, ClamAV 0.103.2

    Links for the day



  10. Lunduke: On Mob Justice in the Tech Industry

    A new video from the former Microsofter who fears the phenomenon that’s adopted by companies like IBM



  11. IRC Proceedings: Friday, April 09, 2021

    IRC logs for Friday, April 09, 2021



  12. EPOLeaks on Misleading the Bundestag — Appendix (Benoît Battistelli's Vichy Syndrome): Georges Henri Léon Battistelli and Charles Robert Battistelli

    Local copies with evidence of or something concrete about Benoît Battistelli’s connection to unsavoury — and by today’s standards outright fascistic — politics



  13. IBM Doubles Down on Masters Being an Acceptable Word in the Context of Technology

    3 days after this post which disproves IBM's stance or shows its double standards it once again says “Masters” in its official blog (won’t that offend and alienate some people as they insist?)



  14. Hate Letter Against Richard Matthew Stallman (RMS) Backfired So Spectacularly That Signers Asked to Revoke Their Own Signatures and the List Was Then Frozen Permanently (Updated)

    "An open letter in support of Richard Matthew Stallman being reinstated by the Free Software Foundation" tops 6,100 signatures (graph generated just moments ago)



  15. EPOLeaks on Misleading the Bundestag -- Part 11: The BMJV's Tweedledee: Dr Christoph Ernst

    The right-hand man of António Campinos plays a role similar to that of Herr Lutz before him



  16. Links 9/4/2021: Tanglet 1.6.0 and HPVM 1.0

    Links for the day



  17. The Libel Against Richard Stallman Did Not Age Well

    Almost 2 years down the line libel about the founder of the FSF remains online, uncorrected (in sites funded by Microsoft and IBM)



  18. The Letter in Support of the FSF and Richard Stallman is Backed by the International Community, Not American Monopolies and Nationalistic Elements

    Free software is for everybody to use, internationally, it is not the asset of a bunch of current and old monopolists (connected to the US military) that also control the media; the nature of the signatures says that out loud



  19. Gemini Over IPFS (Decentralised Web, Accessed Over Gemini Protocol)

    The Gemini protocol (gemini://) can already be used to fetch (at the back end) and present objects from a P2P-like network; we're currently exploring practical use cases and possibilities



  20. News Sites That Talk About Patents Have Become Shameless Self-Promotion 'Plugs' by Law Firms (and Sometimes Outright 'Spam' for Litigation)

    The sources of news about patent affairs have dried up; sites that actually used to investigate and report facts have since then shut down or defected to the Public Relations/marketing industry



  21. Links 9/4/2021: Kubernetes 1.21 and FFmpeg 4.4 Released

    Links for the day



  22. IRC Proceedings: Thursday, April 08, 2021

    IRC logs for Thursday, April 08, 2021



  23. [Meme] Self-styled Judges

    To suit a recurring theme at the EPO we hereby present Roland Lutz, a self-styled judge



  24. EPOLeaks on Misleading the Bundestag -- Part 10: A Faithful Lapdog Despised and Reviled by EPO Staff

    "In any event, the "Nazi" jibes directed against Lutz seem to have triggered Battistelli who decided to take revenge on his perceived enemies inside the EPO by smearing them as “Nazis”."



  25. Links 8/4/2021: GnuPG 2.3.0, Xen 4.15, Xfdashboard 0.9.2

    Links for the day



  26. The Hate Letter Which Backfired

    The FSF is more closely aligned with its founder's vision, his antagonists have left or are leaving, and that old hate letter turned out to be a loud minority (made to appear louder by biased media) emboldened by a gish gallop of lies



  27. IRC Proceedings: Wednesday, April 07, 2021

    IRC logs for Wednesday, April 07, 2021



  28. IBM: We Can Say It... You Cannot

    Blog posts such as this new one help show the hypocrisy or the double standards of IBM, looking to control speech while attacking people's (software) freedom/civil liberties and profiting from atomic bombs



  29. The Collapse of Microsoft Windows

    Although the corporate media keeps insisting that Microsoft is doing well, government (or military) bailouts keep the company afloat while its desperate attempts to remain relevant (as the common carrier languishes) merit a debate



  30. Links 8/4/2021: Mesa 21.0.2, GNU Releases, and Stable Kernels

    Links for the day


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts