summaryrefslogtreecommitdiffstats
path: root/drivers/md/dm.c
diff options
context:
space:
mode:
authorSami Tolvanen <samitolvanen@google.com>2015-03-18 16:52:14 +0100
committerMike Snitzer <snitzer@redhat.com>2015-04-15 18:10:22 +0200
commit65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8 (patch)
tree2a5391011a315f42e409a33d8238544451484c14 /drivers/md/dm.c
parentdm thin: remove stale 'trim' message documentation (diff)
downloadlinux-65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8.tar.xz
linux-65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8.zip
dm verity: add error handling modes for corrupted blocks
Add device specific modes to dm-verity to specify how corrupted blocks should be handled. The following modes are defined: - 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. In addition, each mode sends a uevent to notify userspace of corruption and to allow further recovery actions. The driver defaults to previous behavior (DM_VERITY_MODE_EIO) and other modes can be enabled with an additional parameter to the verity table. Signed-off-by: Sami Tolvanen <samitolvanen@google.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to '')
-rw-r--r--drivers/md/dm.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/md/dm.c b/drivers/md/dm.c
index 944cdb322708..f8c7ca3e8947 100644
--- a/drivers/md/dm.c
+++ b/drivers/md/dm.c
@@ -3483,6 +3483,7 @@ struct gendisk *dm_disk(struct mapped_device *md)
{
return md->disk;
}
+EXPORT_SYMBOL_GPL(dm_disk);
struct kobject *dm_kobject(struct mapped_device *md)
{