I'd really like maintainers to get their hands dirty with AI agents as well to help speed up the reviews.

Over the last year there have been way too many stories and Twitter posts like these.

Yes, maintainers are overloaded, but that's only because we haven't yet built the tools to support them.

Other than such statements, I would, as a builder like to hear the sorts of tools and requirements maintainers are looking for which would make their work easier!

We need to move fast without breaking things.

▲

sockaddr 8 hours ago | parent | next [-]

I'm a huge AI advocate but even I can't get on board with this.

Feel free to fork the kernel and maintain your own vibe-coded disaster.

▲

dathinab 8 hours ago | parent [-]

I'm confused by your answer, the previous post doesn't seem to be about vibe-coding at all.

It seems to be more about:

1. auto grouping duplicate security reports

2. auto validating if they are likely viable or likely nonsense

3. auto checking if they have recently been patched

4. auto assessing if they likely "invalide" for other reasons (e.g. they are for a very old long time no longer maintained Linux version, out of tree drivers, etc.)

I mean practically all of that isn't trivial to get working in a way appropriate for the Linux security mailing list and comes with many not so obvious complications. But also non of that is vibe coding and in most cases this is is more about AI doing a per-assemsment of send security issues to speed up the review of them, then it is about the AI doing the final decision.

	▲	kirtivr 7 hours ago \| parent \| next [-]
		Exactly. At the end of the day, we would rather have a more stable and bug-free kernel than not. It's not that much work for me anymore to report and even fix that obscure monitor driver bug that sometimes causes my machine to bootloop, unless I boot without graphics and start the XOrg server manually. I often find myself surprised at how easily frontier models are able to find bugs across abstraction layers, that only original authors can comprehend. We need more positivity around these contributions as well.
	▲	sirsinsalot 7 hours ago \| parent \| prev [-]
		AI slop causes additional noise on the mailing list. Your suggestion is to use more AI to filter the noise? How about we just reduce the noise?

▲

wang_li 6 hours ago | parent | prev [-]

The world doesn't need to support the projects and research areas that interest you. How about we do something better: No one is allowed to say or write anything about AI or AI generated slop until AI is 100% perfect and produces zero errors and does everything with perfect efficiency.

AI trash like this is like showing up to a baseball game with a pitching machine and demanding that they let you join in and be the pitcher using your machine. Just because your slop cannon is fun and exciting to you doesn't make anyone else obligated to join your club just because you fired your slop on them.