Spoiling Linux Kernel with "sanctioned" code

Is there a CVE for this?

Obvious attack vector for Russia: Submit fixes to severe bugs that can't realistically be fixed any other way.

I guess the Russians will have to learn the Chinese way and perhaps the Chinese language as well?

I've been thinking lately that what underpinned the FOSS golden age was not actually decentralized VCS and high-quality forges, nor even ZIRP, but rather peacetime.

After a period of branches and patchsets, full national hard forks are going to become de rigeur, and linux-derived OSes across the world are going to bloom necessarily, as we no longer have the kind of ambient trust required to collaborate across borders.

Look forward to Euro-linux, Sino-BSD, and I guess probably some sort of GCC-area build as well.

Patches will be accepted across national boundaries with only the highest scrutiny, which itself will likely be provided by nationalized AI platforms.

Gods I hate this era

Perfect usecase for AI, by US legal doctrine, copyright is gone after you feed it through and so should sanctions /s

This post is apparently not publicly shown on the main page for some reason.

[flagged]

Yeah, it sucks.

> This adds ~1ms latency per transfer cycle for rapid bidirectional communication which leads to half the USB 1.1 speed for smaller packets at best.

Still, I don't think this patch should be applied /for everyone/. Maybe compile out-of-tree and load as a kernel module, if possible?