killswitch for short-term emergency vulnerability mitigation

It must be noted that this (both the premise and the conclusion you made from this premise) is your opinion only, which is not necessarily shared neither by the majority of the community, nor by the law and/or legal precedent so far.

Well, that's a whole load of confused statements. As long as a model output isn't derivative of its training data (as court cases have so far mostly confirmed) the US copyright office maintains that machine authored code is uncopyrightable. So that means public domain and combinable with any licence including GPL-2.0.

>> … which clearly excludes LLM-regurgitated slop.

Does it? I understand you wish it was so but so far there hasn't been any clear rulings that have indicated that. If anything it looks like the opposite situation in practice. Refer to https://lwn.net/Articles/1061534/

LLMs should not get a free pass just because they are new and shiny.
* Some of the LLM creators appear to have stolen copyrighted materials (by downloading torrents of copyrighted materials that were not freely available). I would love to see one or more of those culprits bankrupted after being found guilty.
* Many of the LLM creators or their agents have ignored robots.txt and brought the servers of freely available copyrighted materials to their knees (and non copyrighted material too). It seems that none of the culprits will face any noticeable consequences.
* Some LLM creators have fed so many duplicated copies of copyrighted materials into their training that, with careful prompting, the LLM can regurgitate derivative material. However some of that prompting likely would be considered entrapment if done by police authorities to a human.
* Many people believe that LLMs deprive us all of reasonably priced water and/or electricity and that they create massive pollution. Honestly, I’m sceptical of many of these claims. I believe that there is massive overbuilding of datacentres, however it’s not clear that these datacenters are all built for AI. Much of the overbuilding seems to be speculative by 3rd parties that hope to get AI or cloud customers.
* Many people worry that AI will take their job, and I think that some will. However the consensus in the thoughtful press seems to be that the current wave of redundancies is driven by the consequences of overhiring during the COVID period. Of course, CEOs would prefer to have it known that it was AI rather than their mismanagement,

On the other hand, the only case ruling on the copyright status of LLM output that I know about seems to have carefully crafted to state that the specific LLM was not capable being a copyright holder, while allowing that a future tool might be.

Governments and courts in Europe, China, and the USA, largely seem to support the concept that the output of an LLM should be held to the same burden of proof for copyright infringement as a human person. That is: can the output be shown to infringe the expression of a specific work rather than the concepts and ideas.

In summary, I’d request that the virulently anti-LLM commenters treat others with respect and specifically not tag me as a monster because I start from a different place than you.

To be clear, I didn't mean that I used an LLM. I meant that it was something that I, at the time new to kernel development, could do on my own without "vibe coding". Thus if a newbie could do it without an LLM, surely an expert with an LLM could do it just fine without running into the usual slop problems that happen when you ask one "make a patch that does $ill_defined_vaguely_worded_thing kthx".

The nice thing about neural networks is that, once the hardware is built, the only continuous resource they require is power, and power can be supplied by renewable energy. After the AI bubble bursts, I suspect many of the surviving companies that were previously disregarding ethics in favor of aggressive competition will start switching to renewable energy in order to get contracts from companies that want "green" resources.