[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250824010623.GE39973@ZenIV>
Date: Sun, 24 Aug 2025 02:06:23 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Prithvi Tambewagh <activprithvi@...il.com>
Cc: skhan@...uxfoundation.org, brauner@...nel.org, jack@...e.cz,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fs: Document 'name' parameter in name_contains_dotdot()
On Sat, Aug 23, 2025 at 07:52:08PM +0530, Prithvi Tambewagh wrote:
> Add documentation for the 'name' parameter in name_contains_dotdot()
>
> Signed-off-by: Prithvi Tambewagh <activprithvi@...il.com>
Out of curiosity, could you describe the process that has lead to
that patch?
The reason why I'm asking is that there had been a truly ridiculous
amount of identical patches, all dealing with exact same function.
Odds of random coincedence are very low - there's quite lot of
similar places, and AFAICS you are the 8th poster choosing the
same one.
I would expect that kind of response to a "kernel throws scary
warnings on boot for reasonably common setups", but for a comment
about a function being slightly wrong this kind of focus is
strange.
If that's some AI (s)tool responding to prompts along the lines of
"I want to fix some kernel problem, find some low-hanging fruit
and gimme a patch", we might be seeing a small-scale preview of
a future DDoS with the same underlying mechanism...
Powered by blists - more mailing lists