On Fri, Oct 09, 2026 at 06:11:33AM -0500, Sasha Levin wrote:
>
> Ted Ts'o asked if we have a way to handle incorrect Fixes: tags in our stable
> tree work, I pointed out that we have LLM workflows to help us determine the
> correct Fixes: tag when we determine when the issue is first introduced, at
> which point other folks showed interest and asked to share it.
The context behind the request was from a conversation I had with
Hannes Reinecke earlier in the week at Plumbers, who told me that in
his estimation 15-20% of the Fixes tags were actively wrong, and were
often due to contributors running "git blame" and just looking at the
first commit which modified a line touched by the patch --- and
maintainers (including myself) not having the time to verify every
single Fixes tags, or adding any missing Fixes tags.
Hence, having some help, either as a standalone AI skill, or as part
of a Sashiko review, or both, to make sure Fixes tags are correct
would be really helpful.
What follows from this is that for people who are doing backports to
their own kernels (if they can't depend on LTS kernels), especially
for commits before we have Maintainers regularly using the AI skill or
Sashiko can start suggesting proper Fixes commits, they should not
depend on the Fixes tags to determine whether their production kernel
might need a particular security or other bug fix.
- Ted
