#lkml — Public Fediverse posts

@littlealex @cR0w Yup. That is exactly the rule of the game. Very publicly known since ages. BDFL and all.
Everyone who is even modestly involved in it knows Mr Torvalds approach to things past his threshold of fucks to be given.

To summarize: High qualify FOSS 🍿 drama. More in news at eleven. 😂

Here's the relevant actual LKML link: https://lore.kernel.org/linux-media/CA[email protected]/

#lkml #linux #torvalds #foss #fossdrama #ai #llm #opensource

Slop pushers should not be debated, they should be removed without debate.

If I were a #linux kernel developer I would have immediately put up a vote of no-confidence in Linus on the #LKML. Either the majority of kernel devs are for, or against this — pointless debate *always* allows the technofascists to win because they never had any intention of finding a working compromise or best solution.

If Linus is so certain of AI it’s he that should have to fork Linux because I doubt that he’s the majority.

If bad leaders can not be removed, forcibly, from #opensource projects then #FLOSS is no better than fascism.

#programming #noai #linux #lkml #opensource #floss

While this is obviously not something that's taught to enough people in engineering school (let alone business school)...

People who develop technology have a fundamental responsibility to consider the ethical implications of the things they create and use.

Just look at history... Humanity has just sleepwalked through 100 years of ethnic cleansing, radioactive contamination, human experimentation, nuclear and chemical warfare, censorship, human rights violations, and climate change.

Will we learn nothing from all of that?

What will the next century bring if we wait another 100 years to begin asking and answering the ethical questions surrounding the technologies that we are building today?

#technology #ethics #society #history #ai #linux #lkml

#LKML #QOTD from Tytso in reply to a #ext2 backporting request to various older #Linux longterm #kernel series:

""[…] And this is why the patches have not been backported. It requires work, and an AI generated request doesn't change the reality that *someone* has to do that work,

I invite you to figure out a way to figure out an AI mediated tool that can attempt the backport, and then run the moral equivalent of "gce-xfstests -c ext4.all -g auto" to verify that the backport doesn't result in any regressions. (Some previous attempts to backport to older LTS kernels have resulted in the kernels crashing as a result.)

Otherwise, I recommend that most users consider switching to a newer LTS kernel, or if they can't to pay $$$ to an enterprise Linux distribution that pays engineers to do that hard work.""

https://lore.kernel.org/all/alDWUmORy7[email protected]/

Side note, regarding the "switching to a newer LTS kernel" aspect: running at least the latest longterm #LinuxKernel is what most users should do anyway, as explained by this post from @gregkh:

http://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/

#LKML #QOTD from Linus:

""I've pulled this, but under protest. Proper hierarchical filesystems have been available since 1965.""

[This was in a reply to a #Linux PR that added five files starting with "ext_" to kernel/sched/]

https://lore.kernel.org/all/CAHk-%3DwghMm2c%2BAYEcwYY7drSVXB27DYqc-ZXpFiq%[email protected]/

#kernel #LinuxKernel

That moment when old #lkml mails of yourself appear on screen.

:blobeyes:

""The #Linux rule for regressions is basically based on the philosophical question of "If a tree falls in the forest, and nobody is around to hear it, does it make a sound?".""

Linus wrote that today on #lkml while detesting the whole notion of "ABI changes": https://lore.kernel.org/all/CAHk-%3Dwga8Qu0-OSE9VZbviq9GuqwhPhLUXeAt-S7_9%[email protected]/

To quote more: ""Pretty much any change can be an ABI change - even totally new interfaces change behavior in that something that didn't use to do anything now does something.

[…]

So I absolutely detest the whole notion of "ABI changes". It's a meaningless concept, and I hate it with a passion, because it then results in the "opposite" situation where some projects seem to think that ABI changes are perfectly fine as long as they go along with version number changes.

[…]

So the only thing that matters is if something breaks user-*conscious* behavior.""

And when that happens, the distinction between "bug fix" and "new feature" and "ABI change" matters not one whit, and the change needs to be done differently.

#LinuxKernel #kernel #regression

My new favourite Rust hack: you can trick rustfmt into formatting imports with one symbol per line. Found this gem in LKML. It's perfect for large import lists!

#rust #rustfmt #lkml #til

Linus today on #LKML in reply to "A formal request for process clarifications" regarding the non-merge of the TSEM LSM – a Linus Security Module which provides a framework for generic security modeling:

""I already think we have too many of those pointless things. There's a fine line between diversity and "too much confusion because everybody thinks they know best". And the linux security modules passed that line years ago.

So my suggestion is to standardize on normal existing security models instead of thinking that you can do better by making yet another one. Or at least work with the existing people instead of trying to bypass them and ignoring what they tell you.

Yes, I know that security people always think they know best, and they all disagree with each other, which is why we already have tons of security modules. Ask ten people what model is the right one, and you get fifteen different answers.

I'm not in the least interested in becoming some kind of arbiter or voice of sanity in this.

Linus""

https://lore.kernel.org/all/CAHk-=whqz[email protected]/T/#u

Now THAT looks like a tutorial I wanted to have: https://blog.gnoack.org/post/lei/

#publicinbox #lkml #plaintextemail #plaintext #email #gitsendemail

Every goto in the Linux kernel / Just another day on the linux-kernel mailing list: https://www.youtube.com/watch?v=v1Mfirg2-Z8

> Visualization of every goto statement in the Linux 6.17 source code.Commentary from a 2003 linux-kernel mailing list discussion about the use of goto. #lkml #data #music #visualisation

Coming from software engineering, I can't stand this legislative practice of lumping tons of disparate things in one body and pushing them through legislature as one. Specifically #UK
#CrimeAndPolicingBill *is* a series of 190+ *PATCHES* to many laws, wrapped into a single text document with chapters and paragraphs. Look at #LKML and tell me more about your problems, making you lump together adding powers to breach anyone's data integrity, and updating rules on HAVING SEX WITH A CORPSE.

""WE ARE NOT PREEMPTIVELY SUPPORTING BIG-ENDIAN ON RISC-V""

Linus send that to #LKML a few hours ago, after somebody asked if some of the big-endian work will make it into #Linux 6.18.

For the full thread, see: https://lore.kernel.org/lkml/CAHk-%3DwgYcOiFvsJzFb%[email protected]/t/#mce138059dc56014643bbda330810183031ef5c06

There he calls the reasons documented on riscv.org as "craziness" and insane:

""In other words, it is suggesting that RISC-V add a big-endian mode due to

(a) internet protocols - where byte swapping is not an issue

(b) using "some RISC-V implementations don't do the existing Zbb extension" as an excuse

This is plain insanity. First off, even if byte swapping was a real cost for networking - it's not, the real costs tend to be all in memory subsystems - just implement the damn Zbb extension.""

That's from https://lore.kernel.org/lkml/CAHk-%3DwgYcOiFvsJzFb%[email protected]/t/#m2fcaa49a910fec7475d313f01abfc861bd588ad5

#riscv #kernel #LinuxKernel

Linus still did neither remove bcachefs from #Linux #kernel nor pulled the updates for 6.17 Kent submitted.

The latter meanwhile wrote a few mails to #LKML which in diplomatic phrases might be called "not really helpful", like this one https://lore.kernel.org/all/3ik3h6hfm4v2y3rtpjshk5y4wlm5n366overw2lp72qk5izizw@k6vxp22uwnwa/

It resulted in a few good replies from respected developers that are worth a read if you are followed the topic, among them from Josef Bacik (https://lore.kernel.org/all/20250809192156.GA1411279@fedora/ ), Matthew Wilcox (https://lore.kernel.org/all/aJfTPliez_[email protected]/ ), Sasha Levin (https://lore.kernel.org/all/aJgaiFS3aAEEd78W@lappy/ ) and Theodore Ts'o (https://lore.kernel.org/all/2025081002[email protected]/ & https://lore.kernel.org/all/2025081005[email protected]/).

Does anyone have a good way to read kernel mailing list threads on mobile (Android)?

K-9/Thunerbird are better than Gmail at threading and can use fixed font size but it's often not good enough. Lore is an awesome resource but the web view is not great for reading long threads.

Maybe the only way is to use a terminal app to access mutt remotely?

#linuxkernel #kernel #lkml

#Linux #kernel maintainer Kees Cook kicked out of #LKML for some time ... Has his account been #compromised?

https://lore.kernel.org/all/CAHk-=wj4a[email protected]/

Update (2025-06-02): Turns out it was a mishap ... more details here: https://infosec.exchange/@dazo/114613627632241765

#foss #oss

Linus Torvalds has proper motivated reasons for really disliking file systems without a case sensitivity.

Read this with me from the kernel lkml, regarding bcachefs.

Re: [GIT PULL] bcachefs fixes for 6.15-rc4 - Linus Torvalds
https://lore.kernel.org/lkml/CAHk-=wja[email protected]/

🖋️ #bash #sh #zsh #ksh #csh #tcsh #fish #git #Linux #lkml #POSIX #FOSS #100daysofCode #640DaysOfCode #coding #1024DaysOfCode #github #programming #Torvalds #filesystem

[Перевод] Линус Торвальдс жёстко разнёс регистронезависимые ФС

Линус Торвальдс сегодня в привычной для себя прямой и резкой манере высказался о файловых системах с поддержкой case folding (регистронезависимых файлов и папок). Поводом послужила проблема с поддержкой case folding в Bcachefs, обнаруженная на этой неделе и уже имеющая фикс для Linux 6.15. Линус написал огромное сообщение в рассылке разработчиков Linux (LKML), изложив своё мнение о реализации case folding. Стоит отметить, что проблема с case folding в Bcachefs — не первая для Linux: ранее уже возникали баги, связанные с обработкой эмодзи и других специальных символов Unicode.

https://habr.com/ru/articles/904564/

#linux #torvalds #торвальдс #линус #lkml #mail #фс #fat

Ohh, there was another discussion on #LKML about "modern #Linux distros should be more careful mounting untrusted storage devices, as they might contain maliciously corrupted filesystems that can cause the #kernel to fail"

Good entry point to the discussion: https://lore.kernel.org/all/Z8948cR5ak[email protected]/t/#u

"[…] We've tried for years to get userspace to adopt a more security-aware model for untrusted devices, but have made pretty much no progress. […]"

#LinuxKernel

Wenn ihr ansonsten auf der #LKML schreibt, mein Rat: Nur über so was wie Firefox Relay schreiben / Adresse im Mailclient dahin modifizieren (bin mir gerade nicht sicher, ob das dann durchgeht), weil die Webscraper des Mailarchivs euch nachher Spam bescheren.

Wann man auf der #LKML beantragen, dass die eigene Mailadresse da rausgelöscht wird? Seit ich vor ~3 Jahren geschrieben habe, bekomme ich auf der Adresse Spam, es ist ärgerlich, weil ich auch sonst immer aufgepasst habe.

oohhhh it is going to be a good morning catching up!

https://lore.kernel.org/rust-for-linux/CAHk-=wgLbz1Bm8QhmJ4dJGSmTuV5w_R0Gwvg5kHrYr4Ko9dUHQ@mail.gmail.com/
#rustforlinux #rfl #linux #lkml #dramah #shadenfreude #popcorn

Torvalds finally steps in and calls out the very same behaviour that Hector Martin was.

https://lore.kernel.org/rust-for-linux/CAHk-=wgLbz1Bm8QhmJ4dJGSmTuV5w_R0Gwvg5kHrYr4Ko9dUHQ@mail.gmail.com/

Turns out LKML was just having connectivity issues, like very VERY bad latency: several proper responses took 3 weeks to get there. /s

“Wait and see” while people burn out is not a strategy I feel I can get behind.
#linux #rust #lkml

Does anyone have any tips on adding a new game controller to the Linux kernel? I have this Nintendo switch knock off controller that doesn’t work but I would like to use. I tried adding the vendor and device id to xpad.c, but that didn’t work. Any ideas?

#linux #kernel #lkml #driver #programming #gaming #NintendoSwitch

"crazy glibc artifact" shots fired ​:kokoro_lmao:​

https://lkml.org/lkml/2024/12/4/1607

#linux #linuxkernel #lkml

2/ For completeness, as it's easy to miss in Kent's long post:

Kent refuses to send a public apology for a remark to a mm developer that lead to the escalation to the COC. Search for "you should probably send him an apology" in his Patreon post to find a good place to start.

Also note that Kent resurrected the #LKML thread with the remark yesterday; new messages start here: https://lore.kernel.org/all/vvulqfvftctokjzy3ookgmx2ja73uuekvby3xcc2quvptudw7e@7qj4gyaw2zfo/t/#u

Warum das Linux-Kernel-Team russische Maintainer ausgeschlossen
hat, erfahrt ihr von @ktn im aktuellen Open Source Spotlight. 📧

Zum Newsletter: https://heise.de/s/zKAKm

#Linux #LinuxKernel #Maintainer #RusslandSanktionen #Sanktionen #OpenSource #FLOSS #FOSS #LinusTorvalds #RussiaSanctions #LKML

Gah lore.kernel.org is being hugged to death and I want to read #lkml for the drama ;-)

Linus on #LKML today:

"""Honestly, I'm pretty damn fed up with buggy hardware and completely theoretical attacks that have never actually shown themselves to be used in practice.

So I think this time we push back on the hardware people […]

Because dammit, let's put the onus on where the blame lies, and not just take any random shit from bad hardware and say "oh, but it *might* be a problem".

Linus"'"

https://lore.kernel.org/all/CAHk-=wiUa[email protected]/

#Linux #kernel #LinuxKernel