Maintainer workflows discussions
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Leon Romanovsky <leon@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Theodore Ts'o" <tytso@mit.edu>,
	David Hildenbrand <david@kernel.org>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: submitting-patches: ask bug fixes for their user-visible impact
Date: Thu, 19 Nov 2026 14:01:13 +0100	[thread overview]
Message-ID: <av7zGbqXizmXY4R-@1wt.eu> (raw)
In-Reply-To: <20261119125947.GK162713@unreal>

On Thu, Nov 19, 2026 at 02:59:47PM +0200, Leon Romanovsky wrote:
> On Thu, Nov 19, 2026 at 01:34:45PM +0100, Willy Tarreau wrote:
> > On Tue, Nov 17, 2026 at 05:27:21PM +0200, Leon Romanovsky wrote:
> > > > > Since you're already making changes in that area, could you add a sentence
> > > > > asking reporters to provide the full dmesg stack trace?
> > > > 
> > > > In this doc, we already ask them not to [1] :)
> > > 
> > > This is really bad. You assumed they would trim the logs correctly, and I,
> > > as the recipient was expected to trust that they were accurate. They are not.
> > > 
> > > They trim everything, which makes these logs useless to me. As I said, they
> > > include AI-generated reports, cases with reproductions that are impossible
> > > with upstream code, and reports for completely out-of-tree code. Everything
> > > like that was visible in original dump stack and it is lost now.
> > > 
> > > > 
> > > > > Many AI-generated patches reduce it to one or two lines, which gives no
> > > > > indication of whether the report is genuine or fabricated. Early in the AI
> > > > > era, I saw some completely fabricated stack traces.
> > > > 
> > > > Is it still an issue?
> > > 
> > > I don't know about faked, but useless yes, especially in the cases where
> > > in-kernel API is involved.
> > 
> > The situation completely changed over the last year. LLMs that would
> > hallucinate bugs and dmesg in single-turn conversations have been
> > replaced with agents/harnesses calling shell commands and able to
> > capture contents without inventing them. I agree that we should ask
> > them to capture such dmesg which nowadays have no reason to be faked
> > anymore.
> 
> The meaning of "faked" has shifted. As you said, it previously referred to a
> completely imaginary call stack, now it refers to a custom module that abuses
> the in-kernel API. The latter is still "faked" because it cannot be done with
> the current code and unlikely will be possible in the future.

Ah OK we were indeed not speaking about the same cases.

Willy

  reply	other threads:[~2026-11-19 13:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 20:05 [PATCH v2] docs: submitting-patches: ask bug fixes for their user-visible impact Sasha Levin
2026-11-17  9:00 ` Greg Kroah-Hartman
2026-11-17  9:27 ` Leon Romanovsky
2026-11-17 15:07   ` Sasha Levin
2026-11-17 15:27     ` Leon Romanovsky
2026-11-17 16:03       ` Sasha Levin
2026-11-19 12:34       ` Willy Tarreau
2026-11-19 12:59         ` Leon Romanovsky
2026-11-19 13:01           ` Willy Tarreau [this message]
2026-11-19 10:13   ` Krzysztof Kozlowski
2026-11-19 10:29     ` Geert Uytterhoeven
2026-11-19 11:19       ` Leon Romanovsky
2026-11-19 11:19     ` Leon Romanovsky
2026-11-19 12:04       ` Krzysztof Kozlowski
2026-11-19 12:36         ` Willy Tarreau
2026-11-19 12:54           ` Leon Romanovsky
2026-11-19 12:58             ` Willy Tarreau
2026-11-19 13:16             ` Krzysztof Kozlowski
2026-11-19 10:12 ` Krzysztof Kozlowski

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=av7zGbqXizmXY4R-@1wt.eu \
    --to=w@1wt.eu \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=leon@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sashal@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tytso@mit.edu \
    --cc=workflows@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