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 14B72309EED
	for <linux-kernel@vger.kernel.org>; Wed, 19 Nov 2025 08:53:34 +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=1763542416; cv=none; b=J/he5XOdzeDfV7J1Tcf+4fWFpKp1RJfWU37k+GDISpol1JBRLRpfMAozcUJvzDhCPpTmKpR3W2TEQGOEl/6Cslsm52lp/oniRj7kkdwAY/Y95W8xmSZVQFsyroJ3WNnlW9ASPIw1tYurVlXUucOHbLvGofEwjs3f3X/wvht1ooc=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1763542416; c=relaxed/simple;
	bh=P5vu+PostL+hD3pqBrqUn6uwLw28B6pTxXiucL13EzQ=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=h2jqfTI4j/b/jRh02q7YfKYFGX6aIF7RhaV8A+GhzXrx2gNSGfVrFn87OQlkUyvvU6d5WBHMqeBqVIAOq3hM7LODgdv/BhqPnQgEK+XXJG+Ktd78AGx7ij9Wq0v+QFe4igYEIHF5JskaKUl1ne7LerQK16dhBjlmooGrHfQ1CfM=
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 11782227A88; Wed, 19 Nov 2025 09:53:30 +0100 (CET)
Date: Wed, 19 Nov 2025 09:53:28 +0100
From: Christoph Hellwig <hch@lst.de>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, Mikulas Patocka <mpatocka@redhat.com>,
	Benjamin Marzinski <bmarzins@redhat.com>,
	Alasdair Kergon <agk@redhat.com>, DMML <dm-devel@lists.linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Snitzer <snitzer@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH] dm-ebs: Mark full buffer dirty even on partial
 write
Message-ID: <20251119085328.GA24461@lst.de>
References: <20251117105945.10179-1-urezki@gmail.com> <fff990bc-6ff9-7b34-8e80-57078de40928@redhat.com> <aRxa1wPMsJwBubjx@pc636> <73556fc8-5fbf-37cb-26b9-7cdb88f69720@redhat.com> <aRx_lCimJco5BPKA@redhat.com> <230baa83-cd79-f232-5fb8-1476115e1ae7@redhat.com> <20251119054635.GB19993@lst.de> <aR2DIXsymZWD9EvG@pc636>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aR2DIXsymZWD9EvG@pc636>
User-Agent: Mutt/1.5.17 (2007-11-01)

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?