Skip to content
AI.info

The Pulse

Google details Sashiko's agentic reviews of Linux patches

Google says Sashiko completes roughly 1,200 Linux patch reviews a day and checks suspected bugs through multiple specialist agents. Its data shows a decline in follow-up fixes, though the company cautions that other factors may have contributed.

Google details Sashiko's agentic reviews of Linux patches

Sashiko reviews roughly 1,200 Linux kernel patches a day using specialist AI sessions that look for different kinds of bugs, Google says. In a Google Cloud post, the company detailed how the system checks those findings and shared data on its use.

The company says the proportion of merged commits requiring a follow-up fix within 60 days fell from a historical average of 3.4% to 2.2% in Linux 7.2. Google cautioned that other factors can affect the figures and that the entire decline cannot be credited to Sashiko.

Reviewing public patches

Google's AI and Infrastructure team built Sashiko as an open-source code review system powered by Gemini. The company donated it to the Linux Foundation earlier this year.

The system reviews patches sent to public Linux kernel mailing lists, while Google runs the service at sashiko.dev. Reviews are free for developers, and review emails go only to lists whose maintainers opt in.

Google says the service makes its prompts, tool calls, reasoning steps and ruled-out bugs public. More than 100 contributors, including kernel maintainers and engineers, have helped improve the prompts and the system itself. The project initially used open-source Linux review prompts started by Chris Mason, before switching to a system combining automatically generated code notes with maintainers' instructions.

How the checks work

Sashiko separates the search for possible bugs from their verification. It first gathers surrounding code, including modified functions, definitions and direct callers, and loads guides for the relevant subsystem. A planner selects the specialist checks needed and assigns each a reasoning budget based on the patch's complexity.

Up to seven specialist sessions then run in parallel, examining areas such as control flow, resource lifetimes, locking and security. The sessions use git tools to search and read the repository, averaging about 100 tool calls per review, according to Google. Each produces a list of suspected problems and another of concerns it investigated and ruled out, with supporting code.

A lead verifier examines both lists. Difficult cases each go to a separate verification agent, including cases in which a specialist may have dismissed a concern based on an unsupported assumption. Neither a bug claim nor a dismissal is accepted without concrete code proof across all call sites. The resulting report is written in the style expected on a Linux mailing list.

Results and limits

Since March 2026, Sashiko has completed 241,000 patch reviews, and 75 or more kernel subsystem lists have opted in, according to Google's figures. More than 1,500 kernel developers have replied to its reports on mailing lists; the company says their feedback on false alarms has helped improve the prompts and verification engine.

The company says Sashiko is cited in more than 2,000 mainline kernel commits and more than 500 official Linux kernel CVEs for 2026. Those figures cover fixes for existing bugs found as a byproduct of reviewing new changes; bugs caught before a patch is merged are harder to count through commit logs.

The historical fix-rate baseline covers 18 releases, from Linux 6.2 through 6.19, and 254,000 commits. Google reports that the 60-day rate was 2.8% in Linux 7.1 and 2.2% in Linux 7.2, compared with the earlier 3.4% average.

Across 21,500 tracked mainline commits, patches receiving a clean Sashiko review needed a follow-up fix within 60 days 0.9% of the time, the company says. Patches merged despite a critical warning needed a fix 7.6% of the time. During development, the team also built a benchmark from nearly 1,000 real Linux kernel bugs to evaluate major changes to Sashiko.

Source

  1. Google Cloud

Companies in this story

Related stories

Explore

More articles