Linux Foundation's AI policy: "If any pre-existing copyrighted materials[...] are included in the AI tool’s output, [..] the Contributor should confirm that they have have permission from the third party owners" https://www.linuxfoundation.org/legal/generative-ai

"If"? Why not "whenever"? https://github.com/mastodon/mastodon/issues/38072#issuecomment-4105681567 https://dl.acm.org/doi/10.1145/3543507.3583199 https://www.sciencedirect.com/science/article/pii/S2949719123000213#b7 https://www.theatlantic.com/technology/2026/01/ai-memorization-research/685552/

And how would the contributor even be aware, should they research every snippet for hours?

Seems like an impossible policy, or am I missing something...?

#AIslop #LLMslop #LLM #LLMs #slop #generativeAI #Linux #opensource #linuxfoundation

Generative AI Policy | Linux Foundation

Code or other content generated in whole or in part using AI tools can be contributed to Linux Foundation projects. However, there are some unique considerations related to AI generated content that developers should factor into their contributions. 

Seems like LF is on mastodon. @lfeurope May I ask you about your input?
Apparently Linux is sloppening at full speed now... oh dear. I bet that's not going to introduce a higher rate of new hidden bugs at all. (/s) https://finance.biggo.com/news/202605111233_Linux_7.1-rc3_AI_Patch_Surge_New_Normal #Linux #FOSS #FLOSS #AI #noai #antiai #LLM #security #kernel
Linux 7.1-rc3 Explodes with AI-Generated Patches, Torvalds Declares It the New Normal

Linus Torvalds has officially released Linux 7.1-rc3, and with it comes a stark proclamation: the days of modest, predictable patch cycles are over. The Linux kernel is now living in an era of massive, AI-fueled code surges, and Torvalds believes this is not a temporary spike but the new baseline for development. The AI-Driven Productivity Boom For the past few release cycles, Torvalds had noticed an unusual uptick in the volume of incoming kernel patches. Initially, he dismissed it as a temporary anomaly—a "blip" in the data. However, with the release of 7.1-rc3, he has changed his tune. Given that the kernel is well past its major version jump, yet the current release is significantly larger than expected for this stage in the cycle, Torvalds now asserts that this is the new normal. He attributes the surge directly to the widespread adoption of AI coding tools by developers. In previous cycles, this point in the release would see developers consolidating features. Now, AI tools enable them to be "a bit more productive," submitting more code each week and fundamentally altering the pace of kernel development. Networking Dominates, Hardware Support Expands This release cycle is heavily defined by networking. A full third (33%) of all patches are dedicated to networking core and drivers, making it the single largest area of focus. Beyond routine fixes, the update brings notable hardware compatibility improvements. For the first time, Linux 7.1-rc3 includes support for USB-C networking on Apple Macs. It also adds specialized audio handling for high-end DJ equipment, specifically the AlphaTheta (formerly Pioneer DJ) EUPHONIA series. On the architecture front, significant work has been poured into the Chinese LoongArch (LoongArch) CPU architecture, with patches targeting KVM virtualization performance and interrupt handling. Patch Distribution: Networking (33%) dominates the 7.1-rc3 cycle, followed by security/stability fixes and hardware support patches. A Surge in Memory Safety and the Rise of Rust One of the most interesting aspects of this release is the high volume of memory safety patches. These fixes, often targeting "use-after-free" vulnerabilities in drivers like Bluetooth and GPU modules, are a constant headache for kernel maintainers. However, the report notes a silver lining: the concurrent increase in the use of the Rust language within the kernel. Rust has memory safety built into its core design. As more kernel components are rewritten in Rust, the long-term hope is that the need for these high-volume, manual memory safety fixes will gradually diminish, leading to a more stable and secure kernel foundation. Key Hardware Additions: Apple Mac USB-C networking, AlphaTheta/Pioneer DJ EUPHONIA audio support. Looking Ahead: Stability and Timely Release With the patch volume reaching new heights, the immediate concern is whether this will delay the final release of Linux 7.1. Torvalds and the team are hopeful that the larger patch sets will not cause any delays, allowing the stable version to be pushed out to the public on schedule. A timely release is crucial for users eager to get support for new hardware, from the latest Apple Mac accessories to professional DJ equipment. For now, the Linux kernel is officially adapting to a faster, AI-accelerated development rhythm.

BigGo Finance
@ell1e I'm hopeful that the course correction will be swift when things start to fall apart.
@MongooseStudios I tried bringing it up on the LKML now: https://lore.kernel.org/lkml/e12330b9-[email protected]/T/ but so far no reaction
Concerns about AI code in the kernel

@ell1e LLM's exist to easy button and "you're absolutely right" their way into your workflow. It's going to require enough pain be cause to draw battle lines and have higher ups (hopefully) come down on the side of not using it.

And then drama, and hopefully sanity in the wake.

@ell1e
Wondering more and more how long until we have no other choice left than an air gap machine running pre-2020 Linux if we want to keep using a computer without all that hell 😢
@baillehache_pascal if you're on the LKML, please consider speaking up: https://lore.kernel.org/lkml/e12330b9-[email protected]/T/
Concerns about AI code in the kernel

@ell1e
I'm not on that mailing list, and I think would have no weight at all there.
Thumbs up to you for speaking up there.
@baillehache_pascal clearly, I alone don't have any weight either. We could use more voices.
@ell1e I feel hopeless... All I still find the will to do is maintaining my list of links on the subject:
https://baillehachepascal.dev/2026/against_llms.php
Your message too has a nice list of links. I intend to check them later and probably add some of them to my own list.
Baillehache Pascal's personal website

Baillehache Pascal's personal website

@baillehache_pascal not meaning to call you out in particular, but doomerism isn't very helpful for effective advocacy.
@ell1e it's designed to *sound* like a reasonable policy while still allowing corporations to get their slop merged