Re: Full subsystem codebase scan for identifying pre-existing issues?

On Wed, Jul 29, 2026 at 9:43=E2=80=AFPM Derek Barbosa <[email protected]>=
 wrote:
>
> Hi,
>
> On Wed, Jul 29, 2026 at 01:34:10PM -0700, Joanne Koong wrote:
> > Hi,
> >
> > Is there a way for Sashiko to run a full scan of a subsystem/tree to
> > identify all the pre-existing issues so that they can be fixed
> > proactively?
>
> At the moment, no. At least nothing that I am aware of :)
>
> There have been some small conversations about such functionality, but no=
thing
> has really taken shape yet. One of the concerns was trying to validate th=
e sheer
> number of potential-false-positives, and how to present such information =
in an
> actionable manner. IIRC syzbot/syzkaller's way of storing such data was u=
sed as
> a comparison point here.
>
> FWIW, Chris Mason has a repository for a tool that runs such scans on cod=
ebases
> -- paired with tools like semcode. His prompts are the same ones that we
> frequently sync back to Sashiko. It won't solve the other point you made,=
 but it
> may be worth looking into. [0][1]

Hi everyone,

Joanne was an early tester of the review prompts last output fall, and
also of the kres scans (thanks Joanne!).  Unfortunately (fortunately?)
I haven't made much progress in June/July because I was out on PTO,
but I'm ramping back up now.  I had promised Roman I'd try and
integrate with his databases, and I'm picking all of that up again
now.

As Derek mentioned, it won't really solve the question of how sashiko
should present existing issues, but hopefully we can knock off some of
the rough edges.

-chris