Re: [PATCH] dm verity: deferred hash checking for restart/logging mode

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

Re: [PATCH] dm verity: deferred hash checking for restart/logging mode

Hi Bongkyu, [auto build test ERROR on dm/for-next] [also build test ERROR on v4.11-rc8 next-20170421] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Bongkyu-Kim/dm-verity-deferred-hash-checking-

Re: [PATCH] dm verity: deferred hash checking for restart/logging mode

On 04/24/2017 09:34 AM, Bongkyu Kim wrote: > This patch introduces deferred hash checking for dm-verity. > In case of restart and logging mode, I/O return first and hash checking is > deferred. It can improve dm-verity's performance greatly. > > This is my testing on qualcomm snapdragon 821 platfo

[PATCH] dm verity: deferred hash checking for restart/logging mode

This patch introduces deferred hash checking for dm-verity. In case of restart and logging mode, I/O return first and hash checking is deferred. It can improve dm-verity's performance greatly. This is my testing on qualcomm snapdragon 821 platform with UFS 2.0. dd if=/dev/block/dm-0 of=/dev/null b