From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Cc: linux-block@vger.kernel.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: Bug in commit aa511ff8218b ("badblocks: switch to the improved badblock handling
Date: Sun, 7 Jan 2024 09:48:25 +0100 [thread overview]
Message-ID: <9a2884bf-8ab4-4f42-8ebc-bfc92aafdfb5@leemhuis.info> (raw)
In-Reply-To: <3035e75a-9be0-4bc3-8d4a-6e52c207f277@leemhuis.info>
On 23.12.23 09:35, Linux regression tracking #adding (Thorsten Leemhuis)
wrote:
> On 22.12.23 19:31, Ira Weiny wrote:
>> Coly,
>>
>> Yesterday I noticed that a few of our nvdimm tests were failing. I bisected
>> the problem to the following commit.
>>
>> aa511ff8218b ("badblocks: switch to the improved badblock handling code")
>>
>> Reverting this patch fixed our tests.
>
> #regzbot ^introduced aa511ff8218b
#regzbot introduced 3ea3354cb9f0
#regzbot fix: 146e843f6b0927
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2024-01-07 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 18:31 Bug in commit aa511ff8218b ("badblocks: switch to the improved badblock handling Ira Weiny
2023-12-22 18:57 ` Ira Weiny
2023-12-23 0:24 ` Ira Weiny
2023-12-23 9:39 ` Coly Li
2023-12-23 17:13 ` Ira Weiny
2023-12-24 0:18 ` Coly Li
2023-12-23 6:52 ` Coly Li
2023-12-23 8:35 ` Linux regression tracking #adding (Thorsten Leemhuis)
2024-01-07 8:48 ` Linux regression tracking #update (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=9a2884bf-8ab4-4f42-8ebc-bfc92aafdfb5@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=regressions@lists.linux.dev \
/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 NNTP newsgroup(s).