From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1172646AbdDXPy2 (ORCPT ); Mon, 24 Apr 2017 11:54:28 -0400 Received: from mail-pg0-f41.google.com ([74.125.83.41]:33452 "EHLO mail-pg0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1171572AbdDXPyM (ORCPT ); Mon, 24 Apr 2017 11:54:12 -0400 Date: Mon, 24 Apr 2017 08:54:08 -0700 From: Sami Tolvanen To: Milan Broz Cc: Bongkyu Kim , agk@redhat.com, snitzer@redhat.com, dm-devel@redhat.com, shli@kernel.org, linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org, Will Drewry Subject: Re: [PATCH] dm verity: deferred hash checking for restart/logging mode Message-ID: <20170424155408.GA60835@samitolvanen.mtv.corp.google.com> References: <1493019260-43938-1-git-send-email-bongkyu.kim@lge.com> <76b0b4ab-f811-7c8e-c88c-1210a0e67119@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <76b0b4ab-f811-7c8e-c88c-1210a0e67119@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 24, 2017 at 10:05:03AM +0200, Milan Broz wrote: > Isn't one of the goal of integrity checking to PREVENT that userspace > accesses tampered data? Absolutely. It's not acceptable for dm-verity to return unverified data to userspace in restart mode. Sami