Re: [MAINTAINERS SUMMIT] The place of AI code review in the Linux Kernel process

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Wed, Jul 15, 2026 at 04:55:03PM +0000, Roman Gushchin wrote:
> 
> * Handling of pre-existing bugs.
> Currently, Sashiko reports pre-existing bugs alongside new issues
> (while trying hard to highlight that these issues were not introduced by
> the proposed change). This approach comes with significant pros (a
> steady stream of bug fixes) and cons (additional noise and workload for
> maintainers). I am considering a database of pre-existing issues to
> ensure they are reported only once (or once per year), with an option
> for the respective maintainers to flag them as false positives. This
> will also provide maintainers an access to a deduplicated and ranked
> list of potential issues in their subsystem’s codebase.

Having database and either flagging issues or tweaking the prompts would
be nice.

Also I feel that if we simply had separate sections in the review, one
giving feedback (including "all clear") strictly on the patch itself,
and another one stating something like:

*** Pre-existng issues identified during patch analysis (address at will) ***

and then listing all other issues would help recipients (and maintainers
too).

Thanks.

-- 
Dmitry