I am of the opinion that LLMs do not, at all, belong in something as critical or as monumentally complicated as the kernel of an operating system. IMO that is just as stupid as using an LLM in a cryptographic library/implementation. There are, I believe, far, far more ways that that could go wrong than go right. Especially considering that a kernel is pretty much God when it comes to a computer: there is very little a kernel can't do. I'm sure some will argue that it "might" boost productivity (whatever that means), but IMO the cost is way, way too high for that kind of risk. This is, I think, even more important when you consider all the environments the Linux kernel runs in. The shear number of ways that LLM-generated code can introduce subtle bugs that will never be caught because the hardware trusts the kernel and is rarely going to stop it from doing something is practically infinite. To an extent the risk can be mitigated, sort of. But if this goes anywhere and people start using LLMs to generate code in a file system, or network controller, or other very important subsystems, this could get really bad, really fast. I'm sure some will say "Well just don't do that!" but really, we tell people not to do a lot of things with LLMs and they do it anyway so...

Replace "LLM" with "C".

Runs