Greg Kroah-Hartman Tests New 'Clanker T1000' Fuzzing Tool for Linux Patches (itsfoss.com)
(Monday April 13, 2026 @11:00AM (EditorDavid)
from the judgment-days dept.)
The word clanker — a disparaging term for AI and robots — "has made its way into the Linux kernel," [1]reports the blog It's FOSS "thanks to Greg Kroah-Hartman, the Linux stable kernel maintainer and the closest thing the project has to a second-in-command."
> He's been quietly running what looks like an AI-assisted fuzzing tool on the kernel that lives in a branch called " [2]clanker " on his working kernel tree. It began with the ksmbd and SMB code. Kroah-Hartman [3]filed a three-patch series after running his new tooling against it, describing the motivation quite simply. ["They pass my very limited testing here," he wrote, "but please don't trust them at all and verify that I'm not just making this all up before accepting them."] Kroah-Hartman picked that code because it was easy to set up and test locally with virtual machines.
"Beyond those initial SMB/KSMBD patches, there have been a flow of other Linux kernel patches touching USB, HID, F2FS, LoongArch, WiFi, LEDs, and more," [4]Phoronix wrote Tuesday , "that were done by Greg Kroah-Hartman in the past 48 hours....
> Those patches in the "Clanker" branch all note as part of the Git tag: "Assisted-by: gregkh_clanker_t1000"
>
> The T1000 presumably in reference to the Terminator T-1000.
[5] It's FOSS emphasizes that "What Kroah-Hartman appears to be doing here is not having AI write kernel code. The fuzzer surfaces potential bugs; a human with decades of kernel experience reviews them, writes the actual fixes, and takes responsibility for what gets submitted."
> Linus has been thinking about this too. Speaking [6]at Open Source Summit Japan last year , Linus Torvalds said the upcoming [7]Linux Kernel Maintainer Summit will address "expanding our tooling and our policies when it comes to using AI for tooling."
>
> He also mentioned running an internal AI experiment where the tool reviewed a merge he had objected to. The AI not only agreed with his objections but found additional issues to fix. Linus called that a good sign, while asserting that he is "much less interested in AI for writing code" and more interested in AI as a tool for maintenance, patch checking, and code review.
[1] https://itsfoss.com/news/linux-kernel-ai-fuzzing/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/gregkh.git/log/?h=clanker
[3] https://lore.kernel.org/lkml/2026040644-brussels-dab-6f99@gregkh/
[4] https://www.phoronix.com/news/Greg-KH-Clanker-Linux-Bugs
[5] https://itsfoss.com/news/linux-kernel-ai-fuzzing/
[6] https://www.zdnet.com/article/linus-torvalds-ai-tool-maintaining-linux-code/
[7] https://events.linuxfoundation.org/linux-kernel-maintainer-summit/
> He's been quietly running what looks like an AI-assisted fuzzing tool on the kernel that lives in a branch called " [2]clanker " on his working kernel tree. It began with the ksmbd and SMB code. Kroah-Hartman [3]filed a three-patch series after running his new tooling against it, describing the motivation quite simply. ["They pass my very limited testing here," he wrote, "but please don't trust them at all and verify that I'm not just making this all up before accepting them."] Kroah-Hartman picked that code because it was easy to set up and test locally with virtual machines.
"Beyond those initial SMB/KSMBD patches, there have been a flow of other Linux kernel patches touching USB, HID, F2FS, LoongArch, WiFi, LEDs, and more," [4]Phoronix wrote Tuesday , "that were done by Greg Kroah-Hartman in the past 48 hours....
> Those patches in the "Clanker" branch all note as part of the Git tag: "Assisted-by: gregkh_clanker_t1000"
>
> The T1000 presumably in reference to the Terminator T-1000.
[5] It's FOSS emphasizes that "What Kroah-Hartman appears to be doing here is not having AI write kernel code. The fuzzer surfaces potential bugs; a human with decades of kernel experience reviews them, writes the actual fixes, and takes responsibility for what gets submitted."
> Linus has been thinking about this too. Speaking [6]at Open Source Summit Japan last year , Linus Torvalds said the upcoming [7]Linux Kernel Maintainer Summit will address "expanding our tooling and our policies when it comes to using AI for tooling."
>
> He also mentioned running an internal AI experiment where the tool reviewed a merge he had objected to. The AI not only agreed with his objections but found additional issues to fix. Linus called that a good sign, while asserting that he is "much less interested in AI for writing code" and more interested in AI as a tool for maintenance, patch checking, and code review.
[1] https://itsfoss.com/news/linux-kernel-ai-fuzzing/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/gregkh.git/log/?h=clanker
[3] https://lore.kernel.org/lkml/2026040644-brussels-dab-6f99@gregkh/
[4] https://www.phoronix.com/news/Greg-KH-Clanker-Linux-Bugs
[5] https://itsfoss.com/news/linux-kernel-ai-fuzzing/
[6] https://www.zdnet.com/article/linus-torvalds-ai-tool-maintaining-linux-code/
[7] https://events.linuxfoundation.org/linux-kernel-maintainer-summit/