From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6CB9B30B535 for ; Wed, 19 Nov 2025 09:00:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763542818; cv=none; b=RSAkzB/E8PYfCfAZCOEpHGQ/W5KeYS2xOB/85UF4m0XS0EaoqJkt9AfmkSpT6EiU8byaEX56qVx8vUwRIxGGKxkEn1QUhVc2gsj0mkUgysfr4jfkFinksGdqdE3uy1bdOaUhSGx2AM3JSNL3Lr2H9kuEg0Lm81OeidKPQKGGgkk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763542818; c=relaxed/simple; bh=ZUejwk1+gu0Z7E+xfb930LGt9ckUrL4DKqSgrRRnZrM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=YT9Ut20jiiJTK1hM6A5nwyF81xthfJAkjEFUtGov4lLGgH+Ke1xLlKF5OtkFhYpwFdnl8rhJNYcBaMbAoq/Xk1TMFx9CweqESyoyCNpNbyATmhhG6+W8XiG7gZRKKC6O+oxjiX6jHhZHxmur2V5lkf1zK2N/dabbh2D2caWFF54= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de Received: by verein.lst.de (Postfix, from userid 2407) id 1EF046732A; Wed, 19 Nov 2025 10:00:11 +0100 (CET) Date: Wed, 19 Nov 2025 10:00:10 +0100 From: Christoph Hellwig To: Uladzislau Rezki Cc: Christoph Hellwig , Mikulas Patocka , Benjamin Marzinski , Alasdair Kergon , DMML , Andrew Morton , Mike Snitzer , LKML Subject: Re: [RESEND PATCH] dm-ebs: Mark full buffer dirty even on partial write Message-ID: <20251119090010.GA24598@lst.de> References: <20251117105945.10179-1-urezki@gmail.com> <73556fc8-5fbf-37cb-26b9-7cdb88f69720@redhat.com> <230baa83-cd79-f232-5fb8-1476115e1ae7@redhat.com> <20251119054635.GB19993@lst.de> <20251119085328.GA24461@lst.de> Precedence: bulk X-Mailing-List: dm-devel@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) On Wed, Nov 19, 2025 at 09:57:49AM +0100, Uladzislau Rezki wrote: > On Wed, Nov 19, 2025 at 09:53:28AM +0100, Christoph Hellwig wrote: > > On Wed, Nov 19, 2025 at 09:43:13AM +0100, Uladzislau Rezki wrote: > > > Well. LBA is fixed in my case. Just only one format which is 512B. > > > > > > Whereas the I/O can not be performed by using LBAs sizes. It is fixed > > > and bigger. > > > > Then it is not an LBA. The LBA is defined as the minimum block size > > you can do I/O on. Aka your device is really gravely broken. What > > device is this and who is selling it? > > > I define UBS - underlying block size. The lower layer expects BIOs in > that sizes but this is not true. > > I am not allowed to disclose and answer your last question. Well. Let's frame it differently: this device is just to broken to be used with Linux. In theory we could quirk based on the vendor ID to correctly report the logical block size, but for that we'd need the information.