All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Zi Yan <ziy@nvidia.com>
Cc: John Hubbard <jhubbard@nvidia.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	 "David Hildenbrand (Arm)" <david@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org
Subject: Re: AI slop (was Re: [PATCH] mm/huge_memory: let special huge VMAs bypass the THP) policy check
Date: Thu, 6 Aug 2026 18:41:07 +0100	[thread overview]
Message-ID: <anTFxPf5dP_jxVcD@lucifer> (raw)
In-Reply-To: <A403B054-108E-49E8-BFF6-BE5EF8E61C02@nvidia.com>

On Thu, Aug 06, 2026 at 01:08:15PM -0400, Zi Yan wrote:
> On 6 Aug 2026, at 13:05, John Hubbard wrote:
>
> > On 8/6/26 9:50 AM, Lorenzo Stoakes (ARM) wrote:
> >> On Thu, Aug 06, 2026 at 01:45:17PM -0300, Jason Gunthorpe wrote:
> >>> On Thu, Aug 06, 2026 at 04:47:07PM +0200, David Hildenbrand (Arm) wrote:
> >>>> Just to be clear: Unchecked AI slop in any form is making my life
> >>>> worse every day.
> >>>
> >>> I think eveyone's life who contributes reguarly to the kernel.. The
> >>> only ones who seem to benifit are people doing drive by patches!
> >>
> >> And they shouldn't - we should make sure that nobody doing this can
> >> benefit.
> > ...
> >>> Yet responsible use of AI seems genuinely helpful and quality improving :\
> >>
> >> Yes and I use it daily. It's really helpful when kept on a short leash...
> >
> > haha so true. A *very* short leash! :)

Very very :)

> >
> >>
> >> We're going to have to move to a trust model eventually IMO where random
> >> new people just don't get to apply anything until they build trust with
> >> smaller changes (and with measures for established people who start
> >> sloppping).
> >
> > That sounds like a good move! It really is all about who sends these patches,
> > and what their stance is toward creating patches.
> >
> > And furthermore, that's not even a change in policy! Because traditionally,
> > that's how people started anyway: with small patches and patience. It's

I should know, I did the Eudyptula challenge then stuff in the staging drivers
then I wrote a book etc. you know the usual stuff :P

It took years because it's you know a lot. And I still don't really understand
anything (therein lies the zen state of knowing enough to know ones own
incredible ignorance... :)

>
> Patience is the key. Seeing patches refreshed within a day is killing me.

Tell me about it :) the workslopload since the slopularity (circa
late 2025) is slopcrazy.

We so need some kind of a support group... maybe at LPC? :) I nominate the
pub as the venue for this...

>
> > only with AI that they've been able to skip that step, to everyone's
> > detriment.

Yeah. And also there are a number of people who, bless them, simply could
never get to the point of being able to contribute.

I really do think talent is a factor (I know for some this is a
controversial position) as well as bloody-mindedness, a certain way of
thinking about perhaps some masochism thrown in there somewhere ;)

I think only a small % of a small % have what it takes.

In the past those who could not, would not, even if they tried a little
first.

Now those who can not, do, but do so with absolutely no understanding or
sane guardrails (Dunning Kruger comes into play here also).

> >
> > There are some patchsets in my inbox that I instinctively just skipped,
> > because they were huge new patchsets from new AIs (not people, really),
> > only to watch in dismay as they burned up other people's time in
> > review attempts.

I fear doing so in case things end up getting merged mistakenly.

But I am certainly a lot more quickly dismissive of this crap than I used
to be, simply because I only have finite time and an infinite amount of
work to do :)

> >
> > thanks,
> > --
> > John Hubbard
>
>
> Best Regards,
> Yan, Zi

--
Cheers, Lorenzo


      parent reply	other threads:[~2026-08-06 17:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  5:55 [PATCH] mm/huge_memory: let special huge VMAs bypass the THP policy check Cédric Le Goater
2026-08-05 10:41 ` Lorenzo Stoakes (ARM)
2026-08-05 16:21   ` Cédric Le Goater
2026-08-05 16:26     ` Lorenzo Stoakes (ARM)
2026-08-05 16:29       ` Cédric Le Goater
2026-08-06  1:44   ` Matthew Wilcox
2026-08-06  6:29     ` Lorenzo Stoakes (ARM)
2026-08-06 16:19   ` David Hildenbrand (Arm)
2026-08-06 16:34     ` Cédric Le Goater
2026-08-06 16:45       ` David Hildenbrand (Arm)
2026-08-05 12:15 ` Jason Gunthorpe
2026-08-05 16:29   ` Lorenzo Stoakes (ARM)
2026-08-05 16:52     ` Jason Gunthorpe
2026-08-05 16:54       ` Lorenzo Stoakes (ARM)
2026-08-06 14:26 ` David Hildenbrand (Arm)
2026-08-06 14:28   ` Lorenzo Stoakes (ARM)
2026-08-06 14:42     ` Cédric Le Goater
2026-08-06 14:47       ` David Hildenbrand (Arm)
2026-08-06 14:53         ` Cédric Le Goater
2026-08-06 14:59           ` David Hildenbrand (Arm)
2026-08-06 16:45         ` Jason Gunthorpe
2026-08-06 16:47           ` David Hildenbrand (Arm)
2026-08-06 16:50           ` AI slop (was Re: [PATCH] mm/huge_memory: let special huge VMAs bypass the THP) " Lorenzo Stoakes (ARM)
2026-08-06 17:05             ` John Hubbard
2026-08-06 17:08               ` Zi Yan
2026-08-06 17:40                 ` Gregory Price
2026-08-06 17:42                   ` Zi Yan
2026-08-06 17:42                   ` Lorenzo Stoakes (ARM)
2026-08-06 19:28                     ` Gregory Price
2026-08-06 19:33                       ` Lorenzo Stoakes (ARM)
2026-08-06 17:41                 ` Lorenzo Stoakes (ARM) [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=anTFxPf5dP_jxVcD@lucifer \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ziy@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.