linux-kernel - Re: [RFC v2 0/5] md/raid1: introduce a new sync action to repair 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <aYIi1JoZnDMq8rNe@infradead.org>
Date: Tue, 3 Feb 2026 08:31:16 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Zheng Qixing <zhengqixing@...weicloud.com>
Cc: Christoph Hellwig <hch@...radead.org>, song@...nel.org,
	yukuai@...as.com, linan122@...wei.com, xni@...hat.com,
	linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org,
	yi.zhang@...wei.com, yangerkun@...wei.com, houtao1@...wei.com,
	Zheng Qixing <zhengqixing@...wei.com>
Subject: Re: [RFC v2 0/5] md/raid1: introduce a new sync action to repair
 badblocks

On Tue, Feb 03, 2026 at 04:08:23PM +0800, Zheng Qixing wrote:
> Hi,
> 
> 在 2026/2/3 15:31, Christoph Hellwig 写道:
> > Just curious, but what kind of devices do you see that have
> > permanent bad blocks at a fixed location that are not fixed by
> > rewriting the sector?
> 
> The bad_blocks entries record sectors where I/O failed, which
> indicates that the device-internal remapping did not succeed
> at that time.
> 
> `rectify` does not assume a permanently bad or fixed LBA. Its
> purpose is to trigger an additional rewrite, giving the underlying
> device (e.g. FTL or firmware) another opportunity to perform its
> own remapping.

Well, what devices do you see where writes fail, but rewrites
fix them?