summaryrefslogtreecommitdiffstats
path: root/drivers/md/dm-crypt.c
diff options
context:
space:
mode:
authorMikulas Patocka <mpatocka@redhat.com>2017-03-17 17:40:51 +0100
committerMike Snitzer <snitzer@redhat.com>2017-03-24 20:54:23 +0100
commitc2bcb2b702e4684e566d295d687228498184e0c4 (patch)
treed68dcd1dff76ca211a50caac235c36d8f333c8d2 /drivers/md/dm-crypt.c
parentdm integrity: factor out create_journal() from dm_integrity_ctr() (diff)
downloadlinux-c2bcb2b702e4684e566d295d687228498184e0c4.tar.xz
linux-c2bcb2b702e4684e566d295d687228498184e0c4.zip
dm integrity: add recovery mode
In recovery mode, we don't: - replay the journal - check checksums - allow writes to the device This mode can be used as a last resort for data recovery. The motivation for recovery mode is that when there is a single error in the journal, the user should not lose access to the whole device. Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'drivers/md/dm-crypt.c')
0 files changed, 0 insertions, 0 deletions