Sashiko is an open-source, Gemini-powered system that reviews proposed Linux kernel patches to help maintainers spot and check possible bugs. Google says the rollout began in March 2026 and reports roughly 1,200 reviews a day across more than 100 kernel mailing lists; review emails go only to lists whose maintainers opt in. Google’s account of Sashiko

How Sashiko reviews a Linux patch

Sashiko gathers relevant code and subsystem guidance, plans an analysis, runs focused checks, triages possible issues, investigates difficult findings, then produces a report for maintainers. In this workflow, triage means sorting candidate bugs from concerns the system rules out after review.

Google describes up to seven specialist sessions running in parallel, with focus areas such as a patch’s intent, control flow, resource lifetimes, locking, security, and hardware. A review averages about 100 Git-tool calls, according to Google. Those checks are meant to give maintainers more detail to consider; the report is part of the review process, not a replacement for it.

Treat a Sashiko finding as a lead to examine: its process checks candidate bugs before reporting them to maintainers.

What Google’s Linux results measure

Google reports two different sets of follow-up-fix rates. The first compares releases; the second groups commits by their Sashiko review outcome. A follow-up fix is a correction made within 60 days.

Linux release or comparison groupFollow-up fixes within 60 days
Historical average across Linux 6.2–6.193.4%
Linux 7.12.8%
Linux 7.22.2%

The historical average covers 18 releases and 254,000 commits, according to Google. The difference between that 3.4% rate and Linux 7.2’s 2.2% rate is 1.2 percentage points. Google says other factors affect release-to-release rates, so this comparison does not isolate Sashiko’s effect.

A separate Google analysis covered 21,500 tracked mainline commits. It compared follow-up fixes after clean reviews with fixes after commits were merged despite a critical warning:

Sashiko review outcomeFollow-up fixes within 60 days
Clean review0.9%
Merged despite a critical warning7.6%

These percentages describe different review-outcome groups, not the release-wide rates in the first table. Google also reports that Gemini 4 Carbon detected 75.8% of nearly 1,000 historical Linux kernel bugs at the high thinking level. Those bugs had passed human review and were later fixed; the figure is a benchmark result, not a production follow-up-fix rate. Google’s account

What local Sashiko use requires

The Sashiko repository documents local reviews through sashiko review. Its setup instructions use cargo install sashiko, followed by sashiko init and sashiko review from a local checkout. The listed prerequisites are Rust 1.90 or later, Git, and an API key for an LLM provider. Sashiko’s repository and README

For a local review, the README says patch data and relevant surrounding files and history are sent to the provider configured by the user. It also warns that API use can incur charges. Google’s statement that its hosted public mailing-list service costs developers nothing applies to that service; local reviews use the configured provider.

Projects with Sashiko profiles

The repository lists these project profiles:

ProjectListed profile
Linux kernelProduction
SashikoProduction
GCCOfficial pilot
QEMUPilot
Zephyr RTOSPilot