Re: [GIT PULL] Networking deletions for 7.1

[Jason Xing]

On Fri, Apr 24, 2026 at 9:31 AM Roman Gushchin <roman.gushchin@xxxxxxxxx> wrote:
>
>
> 2c on Sashiko:
>
> 1) I'm working on an infrastructure to separate pre-existing issues from
> new issues. My current thinking is to stop reporting these issues with
> reviews of new patches and instead put them into some database and give
> maintainers access to it. Sashiko will automatically deduplicate issues
> and index them by the source file/subsystem. Hopefully it will mean that
> maintainers will see only a limited number of issues in source files
> they support. But I have yet to see how it works in practice.
>
> But I'm somewhat concerned that this way many of these issues will
> remain there forever and by reporting them with new material we actually
> have better chances to get them fixes. Maybe it should be configurable
> per-subsystem. I'm very open for ideas here.

I reckon reporting pre-existing bugs is very meaningful, especially
for maintainers/reviewers/key developers who are trying so hard to
improve this area. But it's a burden for a one-time developer to
understand and fix those pre-existing buggy behavior.

Syzbot has its standalone place for people who are willing to keep
track of known reports: https://syzkaller.appspot.com/upstream/s/net.
Maybe we could do something quite similar?

Thanks,
Jason

>
> 2) Re false positives vs finding more bugs I had the same experience.
> It's easy to tweak it to be more conservative or creative, but it comes
> at a price. It seems like the real answer is simple a better model. We
> saw a big improvement internally switching from Gemini Pro 3.0 to 3.1.
>
> Thanks
>