```
More than 50 networking fixes intended for Linux 7.3-rc7 are being pushed to the next merge window — routine late-cycle pruning by kernel maintainers, but against an increasingly familiar backdrop: the kernel's networking tree is being flooded with AI-generated bug reports and patches that consume review hours without producing working code.
The networking pull request for 7.3-rc7 was submitted and merged ahead of the release candidate's publication, which Phoronix reported is due Sunday. In its coverage, Phoronix noted that the networking subsystem — spanning wired and wireless drivers, protocol implementations, and a long tail of features — "continues to see a lot of activity due to AI-driven bug reports and patches," and that it remains "bombarded" with the resulting churn.
Deferring non-critical fixes during a release candidate's stabilization phase is standard kernel practice, and the deferred patches are queued for the following merge window rather than discarded. What distinguishes this cycle is the volume of low-signal submissions crowding the queue alongside genuine work.
When generating code is cheap, reviewing it is not
AI tools have made it nearly free to produce a plausible-looking patch or a confident-sounding bug report. Establishing that the bug is real, that a proposed fix does not collide with deliberate design decisions, or that it will not introduce regressions under particular workloads remains manual work — and it does not scale with submission volume. Networking maintainers are largely volunteers or engineers for whom upstream review is only a slice of paid responsibilities; every speculative report or half-correct patch costs them minutes or hours.
One detail is worth noting: Phoronix's "bombarded" characterization emerged from routine coverage of a merge window pull request, not from a special investigation or a public appeal. The churn has become a standing condition of the subsystem's normal operation.
A bottleneck the wider ecosystem will recognize
Linux networking is not alone. Across large open-source projects, generative tools have lowered the barrier to submitting code, shifting the constraint from production to review. The kernel's networking tree is simply the largest and most visible place where that shift is showing up — relevant to any infrastructure team running Linux-based systems, including finance, telecom, and cloud-hosted enterprise environments.
For organizations consuming open-source networking code at scale, the practical response is verification discipline rather than more contributions: treat third-party patches as untrusted input, gate them through CI with targeted regression checks, and — most importantly — budget for human review. The scarcest resource upstream is no longer code; it is funded reviewer and maintainer time.
Linux 7.3-rc7 is due for release Sunday, with the deferred networking work carrying over into the next cycle.
Source: Phoronix
```
超過 50 項原定納入 Linux 7.3-rc7 的網絡 subsystem 修補，現被推遲至下一個 merge window——這是 kernel 維護者在版本收尾階段的例行篩選，但背後的情況卻日益令人熟悉：Linux kernel 的 networking tree 正被 AI 生成的 bug 報告和補丁所淹沒，這些提交消耗大量 review 時間，卻往往無法產出真正可用的代碼。
7.3-rc7 的 networking pull request 在該 release candidate 發布前已提交並合併。Phoronix 在相關報道中指出，涵蓋有線及無線驅動、各類協議實現及眾多長尾功能的 networking subsystem，「由於 AI 驅動的 bug 報告及補丁，仍然持續見到大量活動」，並形容該 subsystem 仍「持續受到此類反覆變動所困」。
在 release candidate 的穩定階段推遲非關鍵修補屬於 kernel 開發的標準操作，被延後的補丁將排入下一個 merge window，而非遭丟棄。本輪真正不同之處，在於排隊隊列中夾雜著大量低價值提交，與真正的工作互相競爭 review 資源。
當生成代碼的成本趨近於零，review 成本卻沒有
AI 工具已令製作一份看似合理的補丁或 bug 報告幾乎不花成本，但驗證這些提交的真實性卻仍然完全依賴人手處理——而這部分工作並不會隨提交數量增加而同步擴展。要確認 bug 確實存在、補丁不會與既有設計決策產生衝突，或不會在特定工作負載下引入 regression，均屬耗時的人工作業。Networking 維護者多為義工，或以上游 review 為受薪職責中一小部分的工程師；每一份似是而非的報告或半正確的補丁，都要消耗他們數分鐘至數小時的時間。
值得注意的一個細節是：Phoronix 所用的「猛烈襲擊」一詞，源自於對 merge window pull request 的常規報道，而非特別調查或公開呼籲。這股補丁浪潮已成為該 subsystem 日常運作的常態背景。
更廣泛開放源碼生態的共同瓶頸
Linux 網絡問題並非孤例。在各大開放源碼項目中，生成式工具降低了提交代碼的門檻，令瓶頸從「寫代碼」轉移到「review 代碼」。Linux kernel 的 networking tree 只是這場轉變最大、最顯眼的呈現場所——這個問題與任何運行 Linux 系統的基建團隊息息相關，包括金融、電訊及託管於雲端的企業環境。
對於大規模採用開放源碼網絡代碼的機構而言，實務上的應對措施並非增加貢獻量，而是加強驗證紀律：將所有第三方補丁視為未經信任的輸入，通過自有 CI 進行針對性 regression 測試；更重要的是，為人手 review 預留資源。上游生態系統目前最稀缺的資源已不再是代碼，而是有資助的 reviewer 及維護者時間。
Linux 7.3-rc7 預計於本周日發布，被延後的網絡工作將順延至下一個開發周期。
資料來源：Phoronix