From: antlists <antlists@youngman.org.uk>
To: Coly Li <colyli@suse.de>,
axboe@kernel.dk, dan.j.williams@intel.com,
vishal.l.verma@intel.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, linux-nvdimm@lists.01.org
Subject: Re: [RFC PATCH] badblocks: Improvement badblocks_set() for handling multiple ranges
Date: Tue, 22 Dec 2020 11:12:14 +0000 [thread overview]
Message-ID: <3233b821-4674-b45a-cad4-4943401eff3d@youngman.org.uk> (raw)
In-Reply-To: <c50e7c65-d7bf-e957-d8eb-efed6c24f089@suse.de>
On 20/12/2020 09:46, Coly Li wrote:
> Currently blocks/badblocks.c is used by md raid and nvdimm code, and the
> badblocks table is irrelevant to any of these two subsystems.
Good to know.
>
> If there will be better code for similar or better functionality, it
> should be cool. For me, if the reporting bug is fixed, no difference in
> my view:-)
>
Hopefully that will improve the badblocks handling in md. Sounds like
that could in part be the problems we've been seeing.
If I integrate dm-integrity into md, badblocks should be mutually
exclusive with it, but because dm-integrity is both a performance and
disk-space hit, people might well not want to enable it.
Cheers,
Wol
prev parent reply other threads:[~2020-12-22 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 17:15 Coly Li
2020-12-18 3:25 ` Dan Williams
2020-12-20 9:50 ` Coly Li
2020-12-19 20:02 ` antlists
2020-12-20 9:46 ` Coly Li
2020-12-22 11:12 ` antlists [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=3233b821-4674-b45a-cad4-4943401eff3d@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=dan.j.williams@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-raid@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
/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
all inboxes | Powered by JetHome®