diff options
| author |   Mikulas Patocka <mpatocka@redhat.com> | 2019-05-07 14:28:35 -0400 |
|---|---|---|
| committer |   Mike Snitzer <snitzer@redhat.com> | 2019-05-07 16:05:08 -0400 |
| commit | 30bba430ddf737978e40561198693ba91386dac1 (patch) | |
| tree | 1e87bf7a93dda8fbe8e41c3e9d9f484b1046064a /Kbuild | |
| parent | dm dust: Make dm_dust_init and dm_dust_exit static (diff) | |
| download | linux-dev-30bba430ddf737978e40561198693ba91386dac1.tar.xz linux-dev-30bba430ddf737978e40561198693ba91386dac1.zip | |
dm integrity: correctly calculate the size of metadata area
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.
Fix this so that it takes actual block size into account, which fixes
the following reported issue:
https://gitlab.com/cryptsetup/cryptsetup/issues/450
Fixes: 356d9d52e122 ("dm integrity: allow separate metadata device")
Cc: stable@vger.kernel.org # v4.19+
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions