diff options
| author | Sami Tolvanen <samitolvanen@google.com> | 2015-02-26 13:47:41 +0000 |
|---|---|---|
| committer | Mister Oyster <oysterized@gmail.com> | 2017-12-27 18:43:16 +0100 |
| commit | 01318aaca0af3082f99b0eef937d55da783e7b2b (patch) | |
| tree | 6c15d90cdc0426a56bc6195f699324da625fa5e5 /Documentation/security | |
| parent | a069c6ac6e1b91b0c8ec0587c4ee981b8dcb344c (diff) | |
dm-verity: Add modes and emit uevent on corrupted blocks
Add a device specific mode to dm-verity for handling corrupted
blocks:
DM_VERITY_MODE_EIO is the default behavior, where reading a
corrupted block results in -EIO.
DM_VERITY_MODE_LOGGING only logs corrupted blocks, but does
not block the read.
DM_VERITY_MODE_RESTART calls kernel_restart when a corrupted
block is discovered.
Each mode sends a uevent to notify userspace of corruption and
allow further recovery actions.
Defaults to previous behavior, other modes can be enabled with
an optional parameter added to the verity table.
Change-Id: Ib72ae6ccb865594d28f3553bdcc5a40b1d7af390
Signed-off-by: Sami Tolvanen <samitolvanen@google.com>
Diffstat (limited to 'Documentation/security')
0 files changed, 0 insertions, 0 deletions