176
Linus Torvalds posts his first AI-assisted patch to the Linux kernel, synthetic test clocks 23x performance leap — the bossman makes use of AI tooling himself after issuing clear pro-AI directives (www.tomshardware.com)
submitted 1 day ago by to c/technology@lemmy.world
128 comments fedilink hide all child comments
 

cross-posted from: https://piefed.social/c/linux@programming.dev/p/2509642/linus-torvalds-posts-his-first-ai-assisted-patch-to-the-linux-kernel-synthetic-test-clo

you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 1 day ago* (6 children)

First of all, if a human makes a mistake it's a learning opportunity. When a human misses a bug an LLM hallucinated, noone really learn from it.

I like to compare it with the xray machines at airports. Human operators stare at the screens hunting for weapons and other prohibited items and miss pretty obvious stuff because they get bored out of their minds. They actually added a mechanism to insert fake xray images of weapons ever so often to actually keep the operators interested and alert. Ain't much too different from doing code reviews being the human-in-the-loop/scapegoat.

Also, LLMs don't necessarily generate good code. They excel at generating good-looking mediocre code.

So yeah, I'm gonna go ahead and claim that Linus is more likely to miss a bug a LLM wrote on his behalf than one he wrote himself.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] -2 points 19 hours ago (2 children)

    [...] if a human makes a mistake it's a learning opportunity.

    As per Linux kernel AI policy (and a common fucking sense), you're the one responsible for the code that is submitted from your side, regardless of the tools and pipeline you use. Now get this, when an agent makes a mistake, that you didn't notice, that's still a learning opportunity, especially when you're held accountable for the fuck up.

    Also, LLMs don't necessarily generate good code. They excel at generating good-looking mediocre code.

    True... When you give them a general task that involves solution of technical problems and decision making. But when it's a concrete "do the x thing over here, using this, this, and this", which is then accompanied by your manual review of the changes, they actually do fine, basically allowing you to minimize the tedium, while not robbing you of the most interesting and important parts of development.

    Did Linus's pipeline look like what i described, tho, when he introduced the aforementioned bugs? Was it his technical decision that, by proxy, introduced bugs? I don't know. Regardless of the answers, he's a grown-ass man, and thus is responsible for the consequences of his decisions.

    Is he more likely to introduce a bug now that he uses AI? Only time will show. I might be wrong, but i think Linus is too smart for it to be the case.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 14 hours ago (1 child)

    Despite the "AI policy and common sense" saying that the contributor is responsible for understanding the code committed, Linus did clealry not treat this with the due dilligence required. He used unproven error-prone technology to emit code for a project that millions of users depend on and sent it in despite it having the race condition and the performance regression.

    If Linus was as smart as you seem to believe, he should have checked that code as if it was submitted from his worst enemy, as if it was written by a smarter and malicous adversary or at least a very enthusiastic imbecile. But the LLMs are designed in a way that trick you into believing that they are smart, reasoning and capable and you drop your guard. The code looked good, he got fooled and here we are.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 7 hours ago

    [...] He used unproven error-prone technology [...]

    I'd say, there was plenty of time for people, including Linus, to understand its limits, especially considering that before introducing current AI policy to the kernel maintainers, he used it for his personal project.

    Human-written code is just as error-prone and unreliable, even if it is written by the most experienced dev there is. Do i really need to explain that your own ability to write quality code varies, based off countless factors that affect your mental state? John Dev didn't have his breakfast — boom! Uncaught race condition, segfault, or some other critical bug, or safety vulnerability is introduced into prod.

    What i'm saying is, unreliability of the submitted code is a problem as old as coding itself. It's a well known one, hence all the static analysis tools developed over the decades, code reviews, hell, even opensource itself partially exists to solve this very issue. The fact that the bugs were caught is the living proof of just that.

    If Linus was as smart as you seem to believe [...]

    "Smart" doesn't mean "omniscient", doesn't mean "makes no mistakes". "Smart" is not some kind of divine status. He's still human, he still gets tired, his focus still can dwindle, and important things still slip his mind.

    The code looked good, he got fooled and here we are.

    That's your speculation, probably based off your own experience. Neither of us know the exact circumstances, by which the discussed bugs were introduced.

  • permalink
  • fedilink
  • source
  • parent
  • [–] -5 points 20 hours ago* (last edited 20 hours ago) (1 child)

    First of all, if a human makes a mistake it’s a learning opportunity. When a human misses a bug an LLM hallucinated, noone really learn from it.

    Agents can "learn" from their mistakes within their harness.

    You or the agent can add notes in the memory files or the repo level agents.md files, or standards and conventions files to look for those mistakes.

    Most harnesses these days will spin up a new agent to do a review once the implementation is done, that agent will take memory files, agents.md files and other standards and conventions files into its context to know what to look out for so it won't make the same mistake twice

    Claude code is even doing "dreaming" where it'll do a cron every night to look through all the conversations from the day for stuff it messed up on and add to its memory files to not do those same mistakes.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 6 points 15 hours ago

    You putting quotes around "learn" and "dream" is you admitting that they are not really doing either. LLMs don't think, learn, reason, analyse, design or anything else that require a human mind.

    You making a note in agents.md did not teach the model anything, it's a halfassed attempt to compensate for the fact that LLMs are INCAPABLE of learning. You need to create a new model trained on the new data you wish to incorporate, because when that phase is over the model is locked in.

    Have a look at the claude code leak and you will see how they actually prompt inject constantly to try to keep it on track and not do stupid shit. It has fucking CYBER ALZHEIMERS for gods sake.

    Look at that woman at meta who told an agent to suggest which emails to archive, explicitly forbidding it from deleting anything. Guess what? That internal monologue filled up the context and that instruction fell off the back of the truck, and the clanker happily started shredding emails until they literally pulled the plug.

    LLMs are somehow passing the Turing test for a subset of humans and its embarassing that the bar is apparently that low. The AI labs are doing their best to weaponize that and you fell for it.

  • permalink
  • fedilink
  • source
  • parent