104

Linux 6.19 Gets Rid Of The Kernel's "Genocide" Function (www.phoronix.com)

submitted 3 months ago by cm0002@lemmy.cafe to c/linux@programming.dev

40 comments fedilink hide all child comments

While the Linux kernel has inclusive terminology guidelines for the past five years to replace phrases like master/slave and blacklist/whitelist, there has surprisingly been a "genocide" function within the kernel that was questioned when it was first submitted for inclusion but now removed in Linux 6.19.

Introduced to the Linux kernel back in 2023 was the d_genocide() function as part of various dcache updates to the kernel. The genocide name was questioned when the patches were first posted by longtime Linux developer Al Viro

you are viewing a single comment's thread
view the rest of the comments

[-] GreenCrunch@piefed.blahaj.zone 52 points 3 months ago

To elaborate a bit: what that function does (well, tries to do - it has serious limitations, which is why there is only one caller remaining and that one is used only when nothing else can access the filesystem anymore) is "kill given dentry, along with all its children, all their children, etc."

I sincerely doubt that you will be able to come up with any word describing such action in any real-world context that would not come with very nasty associations.

I feel like there could have been better names possible... d_recursive_kill perhaps? I'm certainly not an expert in this system but I find it challenging to believe that "genocide" was the only word that is adequately descriptive of the functionality.

In fact, I'd argue it's not that descriptive, given that genocide involves targeting some group of people based on some trait, like race, culture, disability, etc. - based on the description "kill given dentry, along with all its children, all their children, etc." that doesn't seem to fit...

perhaps I'm overthinking.