From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Snitzer Subject: Re: dm-integrity: correctly calculate the size of metadata area Date: Tue, 7 May 2019 14:49:34 -0400 Message-ID: <20190507184934.GA24320@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Mikulas Patocka Cc: dm-devel@redhat.com, Milan Broz List-Id: dm-devel.ids On Tue, May 07 2019 at 2:28pm -0400, Mikulas Patocka wrote: > When we use separate devices for data and metadata, dm-integrity would > incorrectly calculate the size of the metadata device as if it had > 512-byte block size - and it would refuse activation with larger block > size and smaller metadata device. > > This patch fixes it so that it takes actual block size into account. > > It fixes https://gitlab.com/cryptsetup/cryptsetup/issues/450 > > Signed-off-by: Mikulas Patocka > Cc: stable@vger.kernel.org # v4.19+ > Fixes: 356d9d52e122 ("dm integrity: allow separate metadata device") Applied, and I rebased your bitmap patches ontop of it.