From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Zi Yan <ziy@nvidia.com>,
linux-kernel@vger.kernel.org
Subject: AI slop (was Re: [PATCH] mm/huge_memory: let special huge VMAs bypass the THP) policy check
Date: Thu, 6 Aug 2026 17:50:23 +0100 [thread overview]
Message-ID: <anS6hcgMkEJocbDJ@lucifer> (raw)
In-Reply-To: <20260806164517.GA140051@nvidia.com>
-cc some people to make it clear this is a general point not aimed at
anybody in particular.
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.
This is why I've revised my 'I will never take somebody's patch from them
and do it myself' policy.
If you do AI slop I will ALWAYS do this (if your AI has found a real issue
and if I am able to without burning out) or just say no and push it to a
TODO.
>
> There is so much more harder work on the maintainer side, and it is
> now even harder to get patches picked up on the submitter side.
Yup it's all awful.
>
> 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...
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).
It sucks but it's the only workable solution IMO.
>
> Jason
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-08-06 16:50 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 ` Lorenzo Stoakes (ARM) [this message]
2026-08-06 17:05 ` AI slop (was Re: [PATCH] mm/huge_memory: let special huge VMAs bypass the THP) " 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)
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=anS6hcgMkEJocbDJ@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jgg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox