14
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Oct 2026
14 points (60.9% liked)
Linux
15293 readers
265 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 3 years ago
MODERATORS
Is this the one where the LLM generated code introduced some severe bug (memory leak or buffer overflow or something), then Linus went on vacation and another dude cleaned it up?
https://lkml.iu.edu/2610.1/13698.html afaik
If yes, then it annoys me that the articles on this are so biased. Because it actually shows the middle ground reality of using LLMs in development instead of the utopia/dystopia extreme views we keep seing online.
Racing condition between threads. But yeah I believe its this one.
It's almost like the person going on vacation comes away with a positive view, and the person cleaning up after them comes away with a negative view . . .
Did AI generate that?
?
Did AI generate that race condition commit of linus?
(sorry, I thought by "that" you meant my comment or the content of the link or something else)
As far as I understand, Linus did an LLM assisted coding session that resulted in code with a race condition. But to what extend he or the LLM is specifically responsibe for the bug, we don't know because he didn't share the session, only the result.
I believe Linus has clearly stated his position that he is specifically responsible for the bug, regardless of whether he uses LLM agents, Ouija boards, or vim to create it.
Thanks, I thought he only now started using LLM's in commits to write code, based on the article.
But I haven't really followed him closely
Maybe Linus saw the race condition but just fixed it badly, again. https://dirtycow.ninja/ "This is an ancient bug that was actually attempted to be fixed once (badly) by me 11 years ago in commit 4ceb5db9757a... but that was then undone due to problems on s390 by [another] commit."