From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sami Tolvanen Subject: Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks Date: Wed, 18 Mar 2015 15:49:51 +0000 Message-ID: <20150318154951.GA29369@google.com> References: <20150316155559.GA32397@google.com> <20150317152749.GA24901@redhat.com> <20150317160649.GA36193@google.com> <20150317180358.GD24901@redhat.com> <20150318132453.GA3176@google.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Mikulas Patocka Cc: device-mapper development , wad@chromium.org, msb@chromium.org List-Id: dm-devel.ids On Wed, Mar 18, 2015 at 11:42:47AM -0400, Mikulas Patocka wrote: > I hope that you at least turn this feature off after a few reboots and > give the user a chance to save his data. Of course. We prompt the user after the reboot and ask them if they want to proceed using the device without verification. We don't want to disable verification before the user has been notified though. Sami