PolyWolfPolyWolf@treehouse.systems
Oct 8, 2026, 12:45 PMoh fun my keyboard broke because of an... incomplete patch series being backported??? https://lore.kernel.org/regressions/14ed23dd-b171-4ffb-b368-5c717f56188c@pepdata.pt/
Replies
- PolyWolfPolyWolf@treehouse.systemsOct 8, 2026, 1:12 PM
supposedly the fix is "queued for the next review round" but in the meantime i'll have to remember to select the old kernel on every boot lol
Oct 8, 2026, 1:16 PM@PolyWolf I love using email patch management
and then running an LLM on all of the patches to pick out which are "important" (because you can't just ask people to label stuff for backport, of course)
and then just indiscriminately applying them without feedback from the authors or testing because see above
(this happens dozens of times per release and kernel culture is far too individualist to be able to change it structurally)
- PolyWolfPolyWolf@treehouse.systemsOct 8, 2026, 1:18 PM
@nota i hadn't realized just how bad the LLM scourge was out there in the wild (besides the random LinkedIn requests i get ofc) but seeing the state of the lkml makes me very worried indeed
- Oct 8, 2026, 1:25 PM
@PolyWolf So this system has worked like this for a looong time. It used to be based on a manually trained model that worked similar to spam detectors. Before that it was manual. It only switched to LLMs a few years back.
The real issue is that, much like with debian, kernel developers don't see themselves as collaborating on a greater whole, they see themselves as rulers of their own small fiefdoms, which creates constant adversarial relationships between different areas of the project.
Oct 8, 2026, 3:19 PM@PolyWolf it's so great how velocity in the linux kernel has increased so much recently