mirror of
https://gitlab.com/cryptsetup/cryptsetup.git
synced 2025-12-05 16:00:05 +01:00
Suspend and resume also dm-integrity device with AEAD.
Currently we suspend top-level device only. With OPAL, the underlying device will start to return errors once OPAL LR is locked. If the dm-integrity device is not suspended, regular journal flush corrupts the device (journal write failure), corrupting data above it. Suspending the whole stack should fix the issue.
This commit is contained in:
@@ -234,6 +234,7 @@ int dm_clear_device(struct crypt_device *cd, const char *name);
|
||||
int dm_cancel_deferred_removal(const char *name);
|
||||
|
||||
const char *dm_get_dir(void);
|
||||
int dm_get_iname(const char *name, char **iname, bool with_path);
|
||||
|
||||
int lookup_dm_dev_by_uuid(struct crypt_device *cd, const char *uuid, const char *type);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user