Re: [PATCH v2] docs: submitting-patches: ask bug fixes for their user-visible impact
From: Sasha Levin
Date: Tue Nov 17 2026 - 11:04:38 EST
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