← Back to context

Comment by rvz

5 hours ago

Clearly, Linus is all over the place here.

He used Claude Code to write one of his patches in [0] and introduced a data race bug in the kernel unbeknownst to himself but this bug was caught by other reviewer [1] before it made it into a new kernel release.

So I'm afraid Linus himself did not understand the changes Claude made to the code he submitted in the mailing list, despite his "principles" in telling others previously that AI was creating slop patches and then now shouting at others who were concerned about using LLMs on code where they do not understand the generated code themselves when it all applied to....himself.

[0] https://lkml.iu.edu/2610.1/13146.html

[1] https://lkml.iu.edu/2610.1/13573.html

Is your belief that Linus never had a bug caught in code review prior to Claude?

  • Why would that be your conclusion?

    • "introduced a data race bug in the kernel unbeknownst to himself but this bug was caught by other reviewer […therefore] Linus himself did not understand the changes Claude made to the code he submitted in the mailing list"

      What other reading of this is there? A bug is being cited as evidence of slop generation, which implies pre-AI the bug would not have happened.

The data race is exactly the kind of subtle bug that even very experienced programmers would make in this circumstance.

The patches that Linus posted are relatively small and self contained and from reading the thread it seems came from a series of in depth conversations with Claude and were carefully reviewed by Linus.

So what we're seeing here is a tricky concurrency bug that even an expert would make. You can't use it as an example of slop