mirror of
https://github.com/torvalds/linux
synced 2024-10-05 10:52:54 +00:00
5c02406428
Otherwise a malicious user could (ab)use the "recalculate" feature that makes dm-integrity calculate the checksums in the background while the device is already usable. When the system restarts before all checksums have been calculated, the calculation continues where it was interrupted even if the recalculate feature is not requested the next time the dm device is set up. Disable recalculating if we use internal_hash or journal_hash with a key (e.g. HMAC) and we don't have the "legacy_recalculate" flag. This may break activation of a volume, created by an older kernel, that is not yet fully recalculated -- if this happens, the user should add the "legacy_recalculate" flag to constructor parameters. Cc: stable@vger.kernel.org Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Reported-by: Daniel Glockner <dg@emlix.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> |
||
|---|---|---|
| .. | ||
| cache-policies.rst | ||
| cache.rst | ||
| delay.rst | ||
| dm-clone.rst | ||
| dm-crypt.rst | ||
| dm-dust.rst | ||
| dm-ebs.rst | ||
| dm-flakey.rst | ||
| dm-init.rst | ||
| dm-integrity.rst | ||
| dm-io.rst | ||
| dm-log.rst | ||
| dm-queue-length.rst | ||
| dm-raid.rst | ||
| dm-service-time.rst | ||
| dm-uevent.rst | ||
| dm-zoned.rst | ||
| era.rst | ||
| index.rst | ||
| kcopyd.rst | ||
| linear.rst | ||
| log-writes.rst | ||
| persistent-data.rst | ||
| snapshot.rst | ||
| statistics.rst | ||
| striped.rst | ||
| switch.rst | ||
| thin-provisioning.rst | ||
| unstriped.rst | ||
| verity.rst | ||
| writecache.rst | ||
| zero.rst | ||