linux-kernel - Re: [RESEND PATCH] dm-ebs: Mark full buffer dirty even on partial write

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

On Wed, Nov 19, 2025 at 10:13:51AM +0100, Uladzislau Rezki wrote:
> On Wed, Nov 19, 2025 at 10:05:30AM +0100, Christoph Hellwig wrote:
> > On Wed, Nov 19, 2025 at 10:01:25AM +0100, Uladzislau Rezki wrote:
> > > Again i rely on this.
> > 
> > I'm not sure what your random quoting of low-quality comments in
> > kernel code is trying to prove here.
> > 
> > Any device that does not support the LBA/sector size correctly is
> > not support by Linux.  We could in theory quirk it in the driver,
> > but for that we'd need to known the vendor/model and a good argument
> > why we can't fix the device reporting, as this should just be firmware.
> > 
> > Secrecy is not going to help with that.
> > 
> I will not resist.
> 
> I tried my best to explain the problem including description and steps
> how to reproduce it in the commit message if someone wants to repeat it
> in qemu with virtual nvme device.

Again, the problem is that your device reports an incorrect block size.

And you're being a complete dick ignoring this and not even telling
us anything about the device.