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: <20251118124623.GA32286@lst.de>
Date: Tue, 18 Nov 2025 13:46:23 +0100
From: Christoph Hellwig <hch@....de>
To: Uladzislau Rezki <urezki@...il.com>
Cc: Mikulas Patocka <mpatocka@...hat.com>, Alasdair Kergon <agk@...hat.com>,
	DMML <dm-devel@...ts.linux.dev>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Mike Snitzer <snitzer@...hat.com>, Christoph Hellwig <hch@....de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH] dm-ebs: Mark full buffer dirty even on partial
 write

On Tue, Nov 18, 2025 at 01:40:28PM +0100, Uladzislau Rezki wrote:
> > If logical < physical, then the device performs read-modify-write cycle 
> > when writing blocks that are not aligned at physical block size.
> > 
> This is not true. It depends on your device and specification. If it
> can't there is the dm-ebs that does the job.

Logical blocks size is the access unit.  Physical block size is a hint
that the device might be doing RWF and thus be slow.  What driver/device
are using?  Whatever it is doing is completely broken.

(that being said aligning things to the physical block size as much
as possible is usually still a good optimization, that's why the
value exists).


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ