Re: [PATCH] mm/damon: introduce DAMON-based NUMA memory tiering module

[Lorenzo Stoakes (Oracle)]

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.