mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Sasha Levin <sashal@kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	workflows@vger.kernel.org, ksummit@lists.linux.dev,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
	broonie@kernel.org
Subject: Re: [PATCH 0/2] agents: add portable agent skills and Fixes attribution
Date: Fri, 9 Oct 2026 12:30:07 -0400	[thread overview]
Message-ID: <askTmFZC6RJKAE_p@mit.edu> (raw)
In-Reply-To: <asi91eAf5veKEUA3@laps>

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
								

      reply	other threads:[~2026-10-09 16:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 22:54 Sasha Levin
2026-10-08 22:54 ` [PATCH 1/2] agents: add infrastructure for agent resources Sasha Levin
2026-10-09 10:27   ` Greg KH
2026-10-09 10:35     ` Sasha Levin
2026-10-09 10:53       ` Greg KH
2026-10-09 13:40   ` Leon Romanovsky
2026-10-09 14:20     ` Sasha Levin
2026-10-09 14:22       ` Konstantin Ryabitsev
2026-10-09 16:36         ` Leon Romanovsky
2026-10-09 22:28           ` Konstantin Ryabitsev
2026-10-08 22:54 ` [PATCH 2/2] agents: add a skill to determine Fixes tags Sasha Levin
2026-10-10  9:40   ` Thorsten Leemhuis
2026-10-10 10:33     ` Michael S. Tsirkin
2026-10-10 13:45       ` Sasha Levin
2026-10-09  9:42 ` [PATCH 0/2] agents: add portable agent skills and Fixes attribution Laurent Pinchart
2026-10-09 10:11   ` Sasha Levin
2026-10-09 16:30     ` Theodore Tso [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=askTmFZC6RJKAE_p@mit.edu \
    --to=tytso@mit.edu \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=ksummit@lists.linux.dev \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sashal@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®