The Linux networking subsystem is being overwhelmed by AI/LLM-generated patches, with maintainer Jakub Kicinski reporting 405 postings tagged [PATCH net] and 687 tagged [PATCH net-next] in just 9 days. An unusually high 37% of posted patches are fixes, likely undercounted because LLM 'researchers' often skip proper tree tagging. This follows the Linux WiFi maintainer introducing a strict 'three second review' rule against AI slop patches, and Linux 7.1 removing old network drivers and the ISDN subsystem partly to reduce AI-generated noise around legacy code. Kicinski notes the team keeps adjusting review criteria but the flood shows no sign of stopping.
Questions this post answers
How many AI-generated patches is the Linux networking subsystem receiving and how is it affecting maintainers?
In a 9-day window around Linux 7.2-rc7, the networking subsystem received 405 postings tagged [PATCH net] and 687 tagged [PATCH net-next]. Maintainer Jakub Kicinski noted that 37% of posted patches being fixes is unusually high, and that number is likely undercounted because LLM submitters often skip proper tree tagging. The team keeps adjusting review criteria but the volume continues to grow. Kernel contributors tracking the AI patch flood in Linux networking follow the fallout on daily.dev.