[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <01c00d16-1441-4ef7-bf28-795b84d9de24@leemhuis.info>
Date: Fri, 27 Oct 2023 10:08:13 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Damien Le Moal <dlemoal@...nel.org>,
Bagas Sanjaya <bagasdotme@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
Linux IDE and libata <linux-ide@...r.kernel.org>
Cc: Hannes Reinecke <hare@...e.de>,
Geert Uytterhoeven <geert+renesas@...der.be>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Tejun Heo <tj@...nel.org>,
Totallyreal Name <kotversuchung@...il.com>,
loqs <kernel_bugzilla@...ropy-collector.net>
Subject: Re: Fwd: bbbf096ea227607cbb348155eeda7af71af1a35b results in "dirty"
shutdown
On 27.10.23 09:41, Damien Le Moal wrote:
> On 10/25/23 09:40, Bagas Sanjaya wrote:
>>
>> I notice a regression report on Bugzilla that seems to have been
>> handled already there [1]. Quoting from it:
> [...]
>>> [1]: https://bugs.archlinux.org/task/80064
>>> [2]: https://bugs.archlinux.org/task/80064#comment223100
>>> [3]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bbbf096ea227607cbb348155eeda7af71af1a35b
>>> [4]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa3998dbeb3abce63653b7f6d4542e7dcd022590
>>
>> See Bugzilla for the full thread.
>>
>> Anyway, I'm adding this regression to regzbot:
>>
>> #regzbot introduced: aa3998dbeb3abc https://bugzilla.kernel.org/show_bug.cgi?id=218038
>> #regzbot title: dirty shutdown due to disabling manage_system_start_stop on SCSI devices
>> #regzbot link: https://bugs.archlinux.org/task/80064
Damien, many thx for handling this regression so quickly.
FWIW, a quick remark, as it might save you (and others seeing this) some
work in the future:
> #regzbot fixed-by: 24eca2dce0f8d19db808c972b0281298d0bafe99
Telling regzbot about this is nice, but not really needed[1], as your
fix afaics contains links to the reports that are tracked by regzbot.
Hence regzbot would have noticed the fix automatically once it lands in
next or mainline[2], just like it noticed and tracked the patches you
posted for review earlier.
Ciao, Thorsten
[1] it just makes it a little more obvious that a fix is now incoming
[2] there is a bug there somewhere that make it fail sometimes, but I'll
sooner or later catch it
Powered by blists - more mailing lists