[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <58B23F1B-9E09-4B30-A1AD-BF900103E971@kernel.org>
Date: Mon, 28 Jul 2025 09:41:05 -0700
From: Kees Cook <kees@...nel.org>
To: dan.j.williams@...el.com, Steven Rostedt <rostedt@...dmis.org>
CC: Jakub Kicinski <kuba@...nel.org>, Sasha Levin <sashal@...nel.org>,
workflows@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, konstantin@...uxfoundation.org, corbet@....net,
josh@...htriplett.org
Subject: Re: [RFC 0/2] Add AI coding assistant configuration to Linux kernel
On July 28, 2025 8:57:21 AM PDT, dan.j.williams@...el.com wrote:
>Kees Cook wrote:
>> Having had to do "find all commits from [set of authors]" research for
>> security audits, I would be very unhappy if I had to do this again in
>> the future for a specific Agent (used any author), and had to loop lore
>> into the process. Yes, it's *doable*, but it'd be very annoying.
> [...]
>So "doable, but very annoying" strikes me as a problem space where an AI
>agent could help. It is not clear to me that a concise commit trailer
>captures everything needed to help both the review and after the fact
>forensics problem, especially when model fine tuning and prompting are
>in play.
Heh, good point. :) We can make all problems *with* agents and problem *for* agents. :P
--
Kees Cook
Powered by blists - more mailing lists