From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Josh Law <objecting@objecting.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 12:29:09 +0000 [thread overview]
Message-ID: <ae7dc7de-966e-4e04-bb55-318d97c61909@lucifer.local> (raw)
In-Reply-To: <b2cdda38-1007-41a7-a992-de953a088a08@kernel.org>
(+cc Christian as referencing his post)
On Thu, Mar 26, 2026 at 01:12:03PM +0100, Krzysztof Kozlowski wrote:
> On 26/03/2026 11:34, Lorenzo Stoakes (Oracle) wrote:
>
> Trimming context, I agree with everything said by Lorenzo, very detailed
> analysis.
Thanks!
[snip]
>
> This patch also targets NUMA which is quite unpopular setup for
> hobbyist. I don't have any NUMA around me for years... Even my build
> machines are not NUMA. How did you get one as a hobbyist?
>
> Also after looking at the code style in this patch, after "reviews" [1]
> and "acks" [2] (quotes on purpose) this account gave on various patches,
> let's look what was admitted 3 weeks ago:
>
> https://lore.kernel.org/all/f8772114-a495-409b-a590-a9b1d8ed1d41@gmail.com/
>
> > I'm learning this Linux system day by day
>
> So learning or adding serious code for MM for NUMA machines?
>
> > I own this device ...
>
> This is about Xilinx AXIS FIFO which is an FPGA IP core. No way you have
> it. It's not popular, no easy way to get it in common embedded boards.
>
> Even assuming if you have embedded FPGA device and work on it, the jump
> from embedded to NUMA is just stunning.
>
> 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".
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
Cheers, Lorenzo
next prev parent reply other threads:[~2026-03-26 12:29 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) [this message]
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)
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=ae7dc7de-966e-4e04-bb55-318d97c61909@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