dm snapshot: fix on disk chunk size validation
commit ae0b7448e91353ea5f821601a055aca6b58042cd upstream.
Fix some problems seen in the chunk size processing when activating a
For a new snapshot, the chunk size can either be supplied by the creator
or a default value can be used. For an existing snapshot, the
chunk size in the snapshot header on disk should always be used.
If someone attempts to load an existing snapshot and has the 'default
chunk size' option set, the kernel uses its default value even when it
is incorrect for the snapshot being loaded. This patch ensures the
correct on-disk value is always used.
Secondly, when the code does use the chunk size stored on the disk it is
prudent to revalidate it, so the code can exit cleanly if it got
corrupted as happened in
Signed-off-by: Mikulas Patocka <firstname.lastname@example.org>
Signed-off-by: Alasdair G Kergon <email@example.com>
Signed-off-by: Greg Kroah-Hartman <firstname.lastname@example.org>
2 files changed