From: Sasha Levin <sashal@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>, Borislav Petkov <bp@alien8.de>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Willy Tarreau <w@1wt.eu>, 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: Tue, 17 Nov 2026 11:03:47 -0500 [thread overview]
Message-ID: <20261117160347.1871652-1-sashal@kernel.org> (raw)
In-Reply-To: <20261117152721.GC162713@unreal>
On Tue, Nov 17, 2026 at 05:27:21PM +0200, Leon Romanovsky wrote:
>On Tue, Nov 17, 2026 at 10:07:49AM -0500, Sasha Levin wrote:
>> On Tue, Nov 17, 2026 at 11:27:23AM +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.
That section came in with
78f101a1b258 ("Documentation/submitting-patches: Add blurb about backtraces in commit messages")
and the tip handbook points at it, so adding Borislav.
Borislav, see above. Leon gets fixes for tool-found bugs with the
backtrace cut down to two or three lines, the way "Backtraces in commit
messages" asks for, and can't vet the report from what's left.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-17 16:03 UTC|newest]
Thread overview: 6+ 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 [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=20261117160347.1871652-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--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=skhan@linuxfoundation.org \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
--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 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.