linux-kernel - Re: [RFC PATCH] badblocks: Improvement badblocks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3233b821-4674-b45a-cad4-4943401eff3d@youngman.org.uk>
Date:   Tue, 22 Dec 2020 11:12:14 +0000
From:   antlists <antlists@...ngman.org.uk>
To:     Coly Li <colyli@...e.de>, axboe@...nel.dk,
        dan.j.williams@...el.com, vishal.l.verma@...el.com
Cc:     linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-raid@...r.kernel.org, linux-nvdimm@...ts.01.org
Subject: Re: [RFC PATCH] badblocks: Improvement badblocks_set() for handling
 multiple ranges

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