From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Damien Le Moal <dlemoal@kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux IDE and libata <linux-ide@vger.kernel.org>
Cc: Hannes Reinecke <hare@suse.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Tejun Heo <tj@kernel.org>,
Totallyreal Name <kotversuchung@gmail.com>,
loqs <kernel_bugzilla@entropy-collector.net>
Subject: Re: Fwd: bbbf096ea227607cbb348155eeda7af71af1a35b results in "dirty" shutdown
Date: Fri, 27 Oct 2023 10:08:13 +0200 [thread overview]
Message-ID: <01c00d16-1441-4ef7-bf28-795b84d9de24@leemhuis.info> (raw)
In-Reply-To: <a704bb1e-4be0-46f8-8118-a18b0547375f@kernel.org>
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
prev parent reply other threads:[~2023-10-27 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 0:40 Fwd: bbbf096ea227607cbb348155eeda7af71af1a35b results in "dirty" shutdown Bagas Sanjaya
2023-10-25 2:11 ` Damien Le Moal
2023-10-27 7:41 ` Damien Le Moal
2023-10-27 8:08 ` Linux regression tracking (Thorsten Leemhuis) [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=01c00d16-1441-4ef7-bf28-795b84d9de24@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bagasdotme@gmail.com \
--cc=dlemoal@kernel.org \
--cc=geert+renesas@glider.be \
--cc=hare@suse.de \
--cc=kernel_bugzilla@entropy-collector.net \
--cc=kotversuchung@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=regressions@lists.linux.dev \
--cc=tj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).