All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Fernando Fernandez Mancera <ffmancera@riseup.net>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Cc: dwmw@amazon.co.uk, mhkelley@outlook.com, mingo@kernel.org
Subject: Re: [PATCH v2] x86/i8253: fix possible deadlock when turning off the PIT
Date: Thu, 27 Mar 2025 23:52:31 +0100	[thread overview]
Message-ID: <87y0wqw0gg.ffs@tglx> (raw)
In-Reply-To: <878qoqxjew.ffs@tglx>

On Thu, Mar 27 2025 at 22:17, Thomas Gleixner wrote:
> Though I really want people to sit down and think about the factual
> impact of a tool based problem observation. Tools are good in detecting
> problems, but they are patently bad in properly analysing them. And no,
> AI is not going to fix that anytime soon, quite the contrary.

May I recommend you to ask your favorite AI model of the moment the
following question:

 "Explain the discussion in the email thread starting at:
  https://lore.kernel.org/all/20250327152258.3097-1-ffmancera@riseup.net"

I'm sure that I'm patently bad at AI prompt engineering, but that does
not justify the utter insanities which these models threw back at me.

 ChapGPT:

   "....
    This patch adds a selftest (automated test) for the nftables
    flowtable feature using a netdevice. It targets the netfilter
    subsystem, which is responsible for packet filtering, NAT, and other
    packet mangling in the Linux kernel."

 Grok:

   See

        https://tglx.de/~tglx/grok.html
   
   for the full glory of AI hallucinations.

At least those two were halfways reasonable:

 Gemini:

   "API REQUEST ERROR Reason: Unknown."

 Claude:

   "I don't have access to the specific URL you've provided ...
    my knowledge cutoff was in October 2024 ..."

Seriously?


  parent reply	other threads:[~2025-03-27 22:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27 15:22 [PATCH v2] x86/i8253: fix possible deadlock when turning off the PIT Fernando Fernandez Mancera
2025-03-27 16:43 ` David Woodhouse
2025-03-27 17:15 ` Thomas Gleixner
2025-03-27 19:54   ` Fernando Fernandez Mancera
2025-03-27 21:17     ` Thomas Gleixner
2025-03-27 21:27       ` Ingo Molnar
2025-03-27 21:36       ` Fernando F. Mancera
2025-03-27 22:52       ` Thomas Gleixner [this message]
2025-03-27 23:15         ` Fernando F. Mancera

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=87y0wqw0gg.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=dwmw@amazon.co.uk \
    --cc=ffmancera@riseup.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhkelley@outlook.com \
    --cc=mingo@kernel.org \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.