Skip to main content

Linux kernel drops “Assisted‑by” tag after Linus Torvalds calls AI disclosure rule “utterly stupid”

Linux kernel drops “Assisted‑by” tag after Linus Torvalds calls AI disclosure rule “utterly stupid”

THE TECH CHRONICLE  ·  technology  ·  Friday, October 16, 2026
Linux kernel drops “Assisted‑by” tag after Linus Torvalds calls AI disclosure rule “utterly stupid”

The criticism sparked a rapid consensus among kernel maintainers to deprecate the “Assisted‑by” tag that had been mandated since …

By TechPulse Blog

On 13 October 2024, Linus Torvalds posted a scathing reply on the Linux kernel mailing list, dismissing the requirement that contributors tag commits generated with AI tools. The criticism sparked a rapid consensus among kernel maintainers to deprecate the “Assisted‑by” tag that had been mandated since January.

Key Takeaways

  • The “Assisted‑by” tag, introduced in January 2024, is being removed from kernel commit documentation.
  • Linus Torvalds labeled the rule “utterly stupid” in a 13 October post, prompting a maintainer consensus.
  • Community debate produced over 50 replies, with notable objections from kernel developer Laurent Pinchart.
  • Other open‑source projects such as System76 and NetBSD have taken opposite stances, banning AI‑generated code.
Metric Value Why it matters
Assisted‑by tag requirement Mandatory since January 2024 Intended to disclose AI assistance in kernel contributions.
Torvalds’ comment date 13 October 2024 Triggered the policy reversal.
Levin’s proposal date 9 October 2024 Started the formal deprecation process.
Community response >50 replies Shows strong engagement and division on AI disclosure.

The “Assisted‑by” Tag: Origin and Intended Purpose

In January 2024, the Linux kernel documentation was updated to require any contributor who employed “any sort of advanced coding tool” – broadly interpreted to include large language models (LLMs) and code‑completion assistants – to append an “Assisted‑by” tag to the commit message. The policy aimed to create a transparent record of AI involvement, ostensibly to aid reviewers and maintainers in assessing the provenance of code changes.

Linus Torvalds’ Reaction and the Maintainers’ Consensus

When a developer queried the necessity of the tag on 13 October, Torvalds responded with a blunt rebuke, asking “Do you not see how UTTERLY STUPID those kinds of rules would be?” His comment, first reported by The Register, set the tone for the ensuing discussion.

Do you not see how UTTERLY STUPID those kinds of rules would be?

Following the outburst, Sasha Levin – a kernel developer who also works at Nvidia – submitted a patch on 9 October proposing the removal of the tag. Levin’s patch note indicated that the Maintainers Summit had reached a consensus to deprecate the rule and strip the related documentation.

Opposition Within the Kernel Community

Not all voices agreed with the rollback. Laurent Pinchart, a veteran kernel developer and founder of Ideas on Board, posted on 13 October that eliminating the tag without an alternative disclosure mechanism would leave a gap in accountability. Pinchart warned that “without that, I can foresee submitters pushing back on the question,” and emphasized the importance of maintaining expectations for contribution quality.

Jeff Layton of Red Hat had earlier outlined three practical reasons for dropping the tag: inconsistent compliance, inadvertent free advertising for proprietary LLM vendors, and an unclear purpose for the collected data.

Torvalds’ Satirical “New Rule” and Broader AI Stance

In response to Pinchart’s concerns, Torvalds offered a tongue‑in‑cheek alternative: “don’t use compilers for any of your kernel submissions,” suggesting that contributors write in assembly and avoid editors to prove they understand the machine at a low level. He clarified that his expectation is for developers to “do their best and understand what they are doing,” regardless of the tools they employ.

During the same week, Torvalds spoke at the Open Source Summit Europe in Prague alongside Dirk Hohndel of Ericsson Software Technology. He admitted a shift in his personal view of AI, stating that he now “really likes using AI” for tasks he finds challenging, such as building a modern UI for a guitar‑pedal project written in C. He described AI‑assisted coding as “a wonderful way to find joy in programming” and likened it to a “gateway drug” for newcomers.

AI’s Practical Impact on Kernel Development

Torvalds acknowledged that AI tools have begun surfacing genuine security bugs and uncovering long‑neglected driver flaws, a claim echoed by TechRadar. He also noted a recent instance where AI contributed to an unusually large release candidate (Linux 7.3‑rc2). While he praised the net improvement AI brings to the code base, he warned that the influx of AI‑generated patches is “stressing maintainers out to the point that it’s a problem.” At the Maintainers Summit, roughly 75 % of talks focused on reducing that stress, including discussions of “Sashiko,” an automated review system whose output now appears directly on the mailing list.

Contrasting Policies in Other Open‑Source Projects

Linux is not alone in grappling with AI‑generated code. System76 has explicitly banned AI‑produced content from its COSMIC desktop environment. NetBSD, since 2024, has prohibited AI‑generated code and reported receiving $120,282 in donations against a $50,000 fundraising target, according to The Register. These divergent approaches highlight a broader industry debate over transparency, security, and the role of proprietary AI services.

Why it matters

The removal of the “Assisted‑by” tag signals a shift in how one of the world’s most critical open‑source projects handles AI‑generated contributions. Without a formal disclosure mechanism, reviewers must rely on code quality and testing rather than provenance metadata. The decision also reflects broader tensions between fostering rapid innovation through AI assistance and maintaining rigorous security and quality standards. Future kernel development may see more automated review tools, but the balance between transparency and practicality remains unsettled.

Frequently asked questions

What was the “Assisted‑by” tag and why was it introduced?

The tag was added to commit messages in January 2024 to flag any changes that involved “advanced coding tools,” such as AI code generators, with the goal of increasing transparency for reviewers.

Who initiated the removal of the tag?

Sasha Levin, a kernel developer and Nvidia engineer, submitted a patch on 9 October proposing the deprecation, which was later endorsed by the Maintainers Summit.

What were the main arguments against keeping the tag?

Jeff Layton cited inconsistent adherence, inadvertent promotion of proprietary LLM vendors, and a lack of clear purpose. Torvalds himself called the rule “utterly stupid,” emphasizing that tool choice should not dictate contribution quality.

How does this change affect contributors?

Contributors no longer need to add the “Assisted‑by” annotation to their commit messages. However, they remain responsible for ensuring the correctness and security of any AI‑assisted code they submit.

Are other projects adopting similar policies?

Some projects, like System76 and NetBSD, have taken the opposite route by banning AI‑generated code outright, illustrating the lack of consensus across the open‑source ecosystem.

Bottom Line

The Linux kernel’s decision to drop the “Assisted‑by” tag, spurred by Linus Torvalds’ blunt criticism, reflects a pragmatic move away from mandatory AI disclosure. While the change simplifies the contribution workflow, it also raises questions about how maintainers will continue to verify the integrity of AI‑augmented patches without a formal tagging system.

Reporting based on: original source.

Comments

Popular posts from this blog

Tracking your plastic: Exposing recycling myths

Tracking your plastic: Exposing recycling myths Marketplace journalists go undercover overseas and pose as recycling brokers to expose the lucrative plastic recycling business. We reveal that Malaysian companies are willing to break the law to buy Canadian plastic and show how some of it is dumped and burned in illegal landfills, where the toxic fumes and run-off appear to be making people sick. Back in Canada, we buy nine tonnes of plastic and secretly track where big companies are taking it. Will it actually get recycled? »»» Subscribe to CBC News to watch more videos: http://bit.ly/1RreYWS Connect with CBC News Online: For breaking news, video, audio and in-depth coverage: http://bit.ly/1Z0m6iX Find CBC News on Facebook: http://bit.ly/1WjG36m Follow CBC News on Twitter: http://bit.ly/1sA5P9H For breaking news on Twitter: http://bit.ly/1WjDyks Follow CBC News on Instagram: http://bit.ly/1Z0iE7O Download the CBC News app for iOS: http://apple.co/25mpsUz Download the CBC News app for ...

Red states now legalizing recreational marijuana too

Red states now legalizing recreational marijuana too The 2020 election proved how broadly accepted recreational marijuana has become throughout the US and across party lines, with measures to legalize recreational pot breezing to victories in Arizona, New Jersey, Montana and South Dakota. (Nov. 12) Subscribe for more Breaking News: https://ift.tt/18F6bii Website: https://apnews.com Twitter: https://twitter.com/AP Facebook: https://ift.tt/2Nv6Z1g Google+: https://ift.tt/seidce Instagram: https://ift.tt/2G5Qog8 ​ You can license this story through AP Archive: https://ift.tt/2ImtqJ5

Two virus survivors get double lung transplants

Two virus survivors get double lung transplants A young paralegal and a car mechanic received lifesaving double lung transplants at Northwestern Medicine in Chicago after COVID-19 destroyed their lungs. (July 30) Subscribe for more Breaking News: https://ift.tt/18F6bii Website: https://apnews.com Twitter: https://twitter.com/AP Facebook: https://ift.tt/2Nv6Z1g Google+: https://ift.tt/seidce Instagram: https://ift.tt/2G5Qog8 ​ You can license this story through AP Archive: https://ift.tt/310Ng1O