linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
To: Josh Law <objecting@objecting.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	 Josh Law <hlcj1234567@gmail.com>, SeongJae Park <sj@kernel.org>,
	 Andrew Morton <akpm@linux-foundation.org>,
	damon@lists.linux.dev, linux-mm@kvack.org,
	 linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	 Kees Cook <kees@kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	 "David Hildenbrand (Arm)" <david@kernel.org>,
	Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH] mm/damon: introduce DAMON-based NUMA memory tiering module
Date: Thu, 26 Mar 2026 16:33:30 +0000	[thread overview]
Message-ID: <cea99016-5407-4392-9b7d-2e6a994f550f@lucifer.local> (raw)
In-Reply-To: <043CED5F-7014-4776-824E-07E027B7BDC3@objecting.org>

On Thu, Mar 26, 2026 at 04:10:42PM +0000, Josh Law wrote:
>
> I will be absolutely transparent with all of you here, The commit descriptions
  (The long ones), Use AI, to be exact! Claude sonnet 4.6,
>
> Additionally, I will make a promise here,
> All of the bug fixes I made, all of my lib/ bug fixes, are made fully by me,
> (minus the commit description for some of them) And I can promise you that on
> the bible, If you have any questions about this, You can always ask me
>
> Forth thing: My patch volume
>
> To justify my patch volume, I am a "excited" Developer, I love the Linux
  kernel, and I have a passion for that, I am very very sorry I filled up your
  mailbox with my slop descriptions

You're obviously lying, and you're not very good at it.

To reiterate:

  Assessment: ~95% probability all contributions are AI-generated. The
  evidence is overwhelming:

  1. Volume is humanly implausible — ~30 emails/day, 5–10 new patch
     submissions per day across unrelated subsystems, from a contributor
     with zero prior history.

  2. Breadth is the strongest signal — no human newcomer simultaneously
     finds subtle bugs in bootconfig, vsprintf, base64, bch, maple_tree,
     assoc_array, io_uring, AND writes a new DAMON NUMA tiering
     module. Each of these requires deep domain-specific knowledge. The
     pattern is consistent with an LLM being pointed at different source
     files to systematically find issues.

  3. Bug-finding pattern — the patches cluster around unchecked return
     values, type mismatches, resource leaks, off-by-ones, signed/unsigned
     issues. This is exactly what an LLM produces when scanning code for
     potential problems.

  4. Rapid revision cycling — bootconfig went from v1 to v8 in ~1 day. This
     matches AI regeneration, not human revision.

  5. Feature additions from a newcomer — glob_match_nocase(),
     glob_validate(), debugfs BUG/WARN interface, and the DAMON NUMA
     tiering module are all non-trivial features. A first-time contributor
     proposing features (not just fixes) across this many subsystems
     simultaneously is essentially unheard of.

  6. Zero ramp-up — the contribution stream started at full throughput with
     no learning curve visible.

Please go away.

and >/dev/null to any further correspondence from you, other than NAK's when
necessary.


  reply	other threads:[~2026-03-26 16:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26  7:27 Josh Law
2026-03-26 10:34 ` Lorenzo Stoakes (Oracle)
2026-03-26 12:12   ` Krzysztof Kozlowski
2026-03-26 12:29     ` Lorenzo Stoakes (Oracle)
2026-03-26 12:40       ` Krzysztof Kozlowski
2026-03-26 12:50         ` Lorenzo Stoakes (Oracle)
2026-03-26 15:14           ` Josh Law
2026-03-26 15:43             ` Krzysztof Kozlowski
2026-03-26 16:10               ` Josh Law
2026-03-26 16:33                 ` Lorenzo Stoakes (Oracle) [this message]
2026-03-26 16:39                   ` Josh Law
2026-03-27  4:09                     ` SeongJae Park
2026-03-27  8:37                     ` David Hildenbrand (Arm)
2026-03-27 15:22                       ` Josh Law
2026-03-30  6:27                         ` David Hildenbrand (Arm)
2026-03-30  7:50                           ` Krzysztof Kozlowski
2026-03-30  8:16                             ` David Hildenbrand (Arm)
2026-03-30 10:14                               ` Herbert
2026-03-30 10:36                                 ` David Hildenbrand (Arm)
2026-03-30 10:41                                   ` Herbert
2026-03-30 10:43                                   ` Herbert
2026-03-30 11:56                                     ` Vlastimil Babka
2026-03-30 10:40                           ` Herbert
2026-03-27 12:50 ` kernel test robot
2026-03-27 17:45 ` kernel test robot

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=cea99016-5407-4392-9b7d-2e6a994f550f@lucifer.local \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=david@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hlcj1234567@gmail.com \
    --cc=kees@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=objecting@objecting.org \
    --cc=sj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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