From: Marek Vasut Subject: Re: [PATCH v3 1/3] ima: use ahash API for file hash calculation Date: Thu, 10 Jul 2014 13:31:25 +0200 Message-ID: <201407101331.25786.marex@denx.de> References: <201407101002.07535.marex@denx.de> <53BE7691.3080604@samsung.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Dmitry Kasatkin , Mimi Zohar , linux-ima-devel@lists.sourceforge.net, "linux-security-module" , "linux-kernel@vger.kernel.org" , "linux-crypto" To: Dmitry Kasatkin Return-path: In-Reply-To: <53BE7691.3080604@samsung.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Thursday, July 10, 2014 at 01:18:41 PM, Dmitry Kasatkin wrote: [...] > > All right, that was my understanding of the entire discussion -- an > > accelerator dying mid-way and what will IMA do about that. > > > >> But as we fallback to early allocated shash, which is not USB yet, > >> then there is no problem. > >> ahash itself does not bring any other additional problem than shash > >> itself. They are compiled builtin together. > > > > Sure, I understood that. But what will happen if the ahash accelerator > > stops working mid-flight, will IMA also go bonkers or is there some > > graceful stop? > > shash fallback will be used. Ah, thank you for clearing this! Best regards, Marek Vasut