linux-kernel - Re: [PATCH RFC md-6.16 v3 00/19] md: introduce a new lockless bitmap

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: <20250512132750.GD31781@lst.de>
Date: Mon, 12 May 2025 15:27:51 +0200
From: Christoph Hellwig <hch@....de>
To: Yu Kuai <yukuai1@...weicloud.com>
Cc: Christoph Hellwig <hch@....de>, xni@...hat.com, colyli@...nel.org,
	agk@...hat.com, snitzer@...nel.org, mpatocka@...hat.com,
	song@...nel.org, linux-kernel@...r.kernel.org,
	dm-devel@...ts.linux.dev, linux-raid@...r.kernel.org,
	yi.zhang@...wei.com, yangerkun@...wei.com, johnny.chenyi@...wei.com,
	"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: [PATCH RFC md-6.16 v3 00/19] md: introduce a new lockless
 bitmap

On Mon, May 12, 2025 at 04:40:02PM +0800, Yu Kuai wrote:
> I don't have such plan for now, actually I tend to remove bitmap file,
> once llbitmap is ready with lightweight overhead, I expect perforamce
> can be better than old bitmap with bitmap file.
>
> If there are cases that llbitmap performace is still much worse than
> none bitmap, and bitmap file can reduce the gap, we'll probable think
> about bitmap file again.

I'd really love to see this replace the old code as soon as possible.
But can we simply drop support for users with the bitmap in a file
in the file system (no matter how much I dislike that use case..)?