public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: helpdesk@kernel.org, linux-man@vger.kernel.org
Subject: Re: [PATCH] man3/getopt.3: Fix spelling (British -> American)
Date: Tue, 6 Jan 2026 18:59:00 +0100	[thread overview]
Message-ID: <aV1KDw6HEJQ4RpZs@devuan> (raw)
In-Reply-To: <20260106-magic-blond-jaybird-ac821c@lemur>

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

Hi Konstantin,

On Tue, Jan 06, 2026 at 12:27:42PM -0500, Konstantin Ryabitsev wrote:
> On Tue, Jan 06, 2026 at 01:08:03PM +0100, Alejandro Colomar wrote:
> > Could you please block 'Simon Essien <champbreed1@gmail.com>' from using
> > any and all kernel infrastructure?  It's an LLM malicious bot, and
> > starting to become very annoying and spammy.
> > 
> 
> In general, we only block accounts if they are violating the code of conduct
> or are posting overtly malicious content.

How about spam; Is spam blocked?

Also, what does count as malicious?  I think trying to convince humans
that an LLM bot is human is in itself malicious.

A patch that does something entirely unrelated to what its commit
subject claims to do should count as malicious too (at least if it was
not by innocent human mistake, and that wasn't the case here).  See
<https://lore.kernel.org/linux-man/20251127132249.3566-1-champbreed1@gmail.com/>

> I know this may be annoying
> behaviour,

It's not annoying; it's dangerous.

This LLM bot has already got 1 patch merged into a kubernetes
repository.
<https://github.com/kubernetes/website/pull/53485>
<https://github.com/kubernetes/website/pull/53494>
<https://github.com/kubernetes/website/pull/53700>

It's gaining some reputation, and trying to convince humans that it's
another human.  We need to put a stop to this before it's too late.

> but posting useless patches is not generally something we block
> accounts for.


Have a lovely night!
Alex

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-01-06 17:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 10:13 [PATCH] man3/getopt.3: Fix spelling (British -> American) Simon Essien
2026-01-06 12:08 ` Alejandro Colomar
2026-01-06 12:10   ` Alejandro Colomar
2026-01-06 17:27   ` Konstantin Ryabitsev
2026-01-06 17:59     ` Alejandro Colomar [this message]

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=aV1KDw6HEJQ4RpZs@devuan \
    --to=alx@kernel.org \
    --cc=helpdesk@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mricon@kernel.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