On Mon, Mar 16, 2015 at 03:55:59PM +0000, Sami Tolvanen wrote: > 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. What's the idea behind kernel restart mode ? If a corrupted block is in the path of boot, will we not get into a continuous reboot cycle. Thanks Vivek -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
