News › linux
By The Linux Camp News, October 9, 2026
Sasha Levin's October 8 proposal would let coding agents return evidence-backed Fixes tags from Git history. The skill recommends attribution; the calling workflow edits the commit.
Sasha Levin submitted a two-patch Linux kernel proposal on October 8, 2026, adding an agents/skills/ directory and a find-fixes skill for coding assistants. This is a proposed patch-preparation facility, not a kernel release announcement: its output is commit attribution backed by repository history. 2
A Fixes tag identifies the earlier commit responsible for the problem a patch repairs. The proposed skill examines Git history and returns that tag together with its evidence. It does not modify commits itself; the calling workflow applies the result. That separation makes attribution a distinct step rather than treating a generated commit message as the whole task. 1 2
The useful distinction for patch authors is between introducing a bug and merely moving buggy code. Levin's example involved a nouveau buffer allocated with kvmalloc() but freed with kfree() on two error paths. He says both blame and the published fix identified a later function split, although that split copied the affected function unchanged. Stopping at that refactor would therefore misidentify the bug's origin. 2
Levin reports testing two agents with the same fix staged, unchanged skill files, and no supplied commit message or existing Fixes tag. That is a narrowly scoped demonstration of attribution, not a measurement of accuracy across kernel patches. 2
For reviewers evaluating such output, check whether the cited commit introduced the faulty operation rather than just relocating it. The quoted agent response attributed the bad frees to 50f290053d79 and explicitly based that judgment on history, not a reproducer. Treat those as separate questions: identifying where a defect began does not establish that the proposed repair works at runtime. 2
The reported testing built only one object file, without a full kernel or module link or hardware execution. Integration is also unsettled: Levin offered to move the resources from the source-tree root into Documentation/. The material retrieved October 9 establishes a proposal, not acceptance or availability in a released kernel, so it supplies no deployment or upgrade instruction for operators. 2 1