From: Josh Law <objecting@objecting.org>
To: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: 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 15:14:01 +0000 [thread overview]
Message-ID: <04B79050-4353-4FD2-A596-1474BDB94B3F@objecting.org> (raw)
In-Reply-To: <14366e29-4ee2-490e-8e4a-0c5cace1f313@lucifer.local>
On 26 March 2026 12:50:40 GMT, "Lorenzo Stoakes (Oracle)" <ljs@kernel.org> wrote:
>On Thu, Mar 26, 2026 at 01:40:19PM +0100, Krzysztof Kozlowski wrote:
>> On 26/03/2026 13:29, Lorenzo Stoakes (Oracle) wrote:
>> >>
>> >> Answering to reviewers with whatever confirmation they look for is also
>> >> a warning sign of non-trustworthy behavior. Or rather behavior trying to
>> >> get trust.
>> >>
>> >> [1]
>> >> https://lore.kernel.org/all/D47F8215-FD08-45ED-AB01-0A5C48CD41DD@objecting.org/
>> >>
>> >> [2]
>> >> https://lore.kernel.org/all/2F84DD09-2880-45E0-AA98-204F10848F85@objecting.org/
>> >>
>> >> Best regards,
>> >> Krzysztof
>> >
>> > Yeah this is really adding up to somebody abusing the kernel process. I think
>> > 'Josh Law' or any other pseudonym that can be traced back to whoever's behind
>> > this should be banned from the mailing list altogether.
>> >
>> > Also, as per Christian ([3]), it seems this guy was using the pseudonym
>> > "techyguyperplexable".
>>
>> Yes, repos on that Github carry commits like:
>>
>> commit c04af501bacbef54cf97cdfb904ddf295f8327c1
>> Author: techyguyperplexable <objecting@objecting.org>
>> AuthorDate: Sun Jan 11 04:21:53 2026 +0530
>> Commit: techyguyperplexable <objecting@objecting.org>
>> CommitDate: Sun Jan 11 04:21:53 2026 +0530
>>
>> ANDROID: sched/rt: reduce lock hold time in update_curr_rt
>>
>> Move resched_curr and do_start_rt_bandwidth outside the spinlock
>> critical section to reduce lock contention
>>
>> Change-Id: I8dfb4e33460ae4eeb0bb854cc2cb084ab5edf7e4
>> Signed-off-by: techyguyperplexable <objecting@objecting.org>
>>
>
>Thanks, it looks pretty clear cut then that 'Josh Law' is an openclaw bot.
>
>To think he was scheduled to be added as a reviewer for literally all of lib/
>recently (5) until various of us pushed back on it :/
>
>[5]: https://lore.kernel.org/all/20260308202425.C9EE4C116C6@smtp.kernel.org/
>
>Is it really that easy to game the system?...
>
>I hate the asymmetry of this - we have to jump on these every time and they can
>send WAY more mail than we can reasonably reply to.
>
>I think we need a clear 'yeeting' mechanism to block these people on everything
>once discovered.
>
>Sadly the kernel has been historically very poor on getting rid of problem
>people (The CoC is essentially a swear monitor at this stage).
>
>In the face of this new kind of threat we probably need to do a lot better.
>
>> >
>> > There's a github with the same name ([4]), and that same user made a comment on an
>> > openclaw issue relating to linking it to gemini ([5]).
>> >
>> > So it seems likely he/she is likely using openclaw to fully automate this 'Josh
>> > Law' user and we're speaking to a bot here.
>> >
>> > (Screenshots have been taken for the (possibly inevitable) deleting that will
>> > happen later.)
>> >
>> > [3]:https://lore.kernel.org/all/20260313-halskette-annahme-94e782eb4ae4@brauner/
>> > [4]:https://github.com/techyguyperplexable
>> > [5]:https://github.com/openclaw/openclaw/issues/44134#issuecomment-4106247302
>>
>>
>>
>> Best regards,
>> Krzysztof
>
>Thanks, Lorenzo
Hello! Wow i came back to a lot.
I can promisw you now i am a human, hand on the bible, and i will improve!
So i will add assisted by to any commit descriptions written by AI, or anything even touching AI, i understand your apprehension and i apoligize very deeply.
V/R
Josh Law
next prev parent reply other threads:[~2026-03-26 15:14 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 [this message]
2026-03-26 15:43 ` Krzysztof Kozlowski
2026-03-26 16:10 ` Josh Law
2026-03-26 16:33 ` Lorenzo Stoakes (Oracle)
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=04B79050-4353-4FD2-A596-1474BDB94B3F@objecting.org \
--to=objecting@objecting.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=ljs@kernel.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