Re: AI slop (was Re: [PATCH] mm/huge_memory: let special huge VMAs bypass the THP) policy check

Gregory Price <[email protected]>
Newsgroups gmane.linux.kernel,gmane.linux.kernel.mm
Message-ID <anTgXv9loeo4U6YI@fedora>
On Thu, Aug 06, 2026 at 06:42:49PM +0100, Lorenzo Stoakes (ARM) wrote:
> On Thu, Aug 06, 2026 at 12:40:16PM -0500, Gregory Price wrote:
> >
> > mm gets everything
> > mm-review is curated from mm to reduce noise
> >
> > Maybe would have to leverage a model though to surface critical things.
> >
> > Just an idea.
> 
> No I don't want slop going anywhere, at all. Nothing.
> 
> If you slop the reward should be silence ideally. And certainly not anything you
> slopped going to any kind of branch... :)
> 
> The slopularity is upon is Gregory. Behold the desert of the real etc.
>

I understand the sentiment, but then we have to reduce this to practice.

And unfortunately, I'm about 99% sure that identifying slop is rapidly
going to approach undecidability.  We're lucky it still emits em-dashes.

Unless we plan on converting the list to semi-public (which feels the
anti-thesis of Linux), i'm not sure how you get there from here.

So the risk is - do you over-bury and make it invisible, knowing we'll
miss legitimate bugs and fixes - or do you do something (anything) that
helps you ignore it while still being inspectable and curated.

And burning tokens to fight tokens is just blatantly a losing battle.

~Gregory
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.