From: Pavel Machek <pavel@ucw.cz>
To: Shuah <shuah@kernel.org>
Cc: sashal@kernel.org, stable@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
conduct@kernel.org, ebiederm@xmission.com
Subject: Re: Sasha Levin is halucinating, non human entity, has no ethics and no memory
Date: Sun, 27 Jul 2025 11:08:16 +0200 [thread overview]
Message-ID: <aIXsgI1n68Dy3l7+@duo.ucw.cz> (raw)
In-Reply-To: <46f581c6-bb61-4163-91a5-27b90838dca8@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]
Hi!
On Wed 2025-07-09 15:14:38, Shuah wrote:
> On 7/8/25 14:39, Pavel Machek wrote:
> > Hi!
> >
> > So... I'm afraid subject is pretty accurate. I assume there's actual
> > human being called "Sasha Levin" somewhere, but I interact with him
> > via email, and while some interactions may be by human, some are
> > written by LLM but not clearly marked as such.
> >
> > And that's not okay -- because LLMs lie, have no ethics, and no
> > memory, so there's no point arguing with them. Its just wasting
> > everyone's time. People are not very thrilled by 'Markus Elfring' on
> > the lists, as he seems to ignore feedback, but at least that's actual
> > human, not a damn LLM that interacts as human but then ignores
> > everything.
> >
>
> You aren't talking to an LLM - My understanding is that Sasha is sending
> these patches (generated with LLM assist) and discussing them on mailing
> lists.
At this point, I'd like to know (a) what steps (if any) were taken to
prevent LLM hallucinations from reaching the lists, and (b) what steps
(if any) were taken to make sure patches Signed-off by developer were
actually reviewed by said developer, and not applied simply due to
said hallucinations.
Confusion caused LLM hallucinations can be seen for example in thread
"[PATCH AUTOSEL 6.15 6/8] PM: Restrict swap use to later in the
suspend sequence", it includes as great stuff as fake http links.
I have seen solution proposed for (a), but have not seen any solution
proposed for (b) and that's actually more serious problem.
One solution would be to use separate email address "Autosel bot <>"
for both From and Signed-off, so there's no confusion between content
generated by developer and content generated by LLM.
Best regards,
Pavel
--
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, and Musk!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-07-27 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 20:39 Sasha Levin is halucinating, non human entity, has no ethics and no memory Pavel Machek
2025-07-09 21:14 ` Shuah
2025-07-10 6:24 ` Pavel Machek
2025-07-27 9:08 ` Pavel Machek [this message]
2025-07-29 17:23 ` Shuah
2025-07-10 17:56 ` Jonathan Corbet
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=aIXsgI1n68Dy3l7+@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=conduct@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.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