From: Mike Snitzer <snitzer@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, Milan Broz <mbroz@redhat.com>
Subject: Re: dm-integrity: correctly calculate the size of metadata area
Date: Tue, 7 May 2019 14:49:34 -0400 [thread overview]
Message-ID: <20190507184934.GA24320@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1905071358500.26614@file01.intranet.prod.int.rdu2.redhat.com>
On Tue, May 07 2019 at 2:28pm -0400,
Mikulas Patocka <mpatocka@redhat.com> 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 <mpatocka@redhat.com>
> 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.
prev parent reply other threads:[~2019-05-07 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 18:28 [PATCH] dm-integrity: correctly calculate the size of metadata area Mikulas Patocka
2019-05-07 18:49 ` Mike Snitzer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190507184934.GA24320@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mbroz@redhat.com \
--cc=mpatocka@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox