Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030467Ab3HIGnt (ORCPT ); Fri, 9 Aug 2013 02:43:49 -0400 Received: from ringil.hengli.com.au ([178.18.16.133]:55965 "EHLO fornost.hengli.com.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1030437Ab3HIGni (ORCPT ); Fri, 9 Aug 2013 02:43:38 -0400 Date: Fri, 9 Aug 2013 16:43:37 +1000 From: Herbert Xu To: Fionnuala Gunter Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, mhcerri@linux.vnet.ibm.com Subject: Re: [PATCH v2] drivers/crypto/nx: saves chaining value from co-processor Message-ID: <20130809064337.GC23834@gondor.apana.org.au> References: <1375917350.16050.14.camel@what-is-leg> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1375917350.16050.14.camel@what-is-leg> 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 Content-Length: 1133 Lines: 27 On Wed, Aug 07, 2013 at 06:15:50PM -0500, Fionnuala Gunter wrote: > This patch fixes a bug that is triggered when cts(cbc(aes)) is used with > nx-crypto driver on input larger than 32 bytes. > > The chaining value from co-processor was not being saved. This value is > needed because it is used as the IV by cts(cbc(aes)). > > Signed-off-by: Fionnuala Gunter > Reviewed-by: Marcelo Cerri > --- > v2. changed signed-off-by to reviewed-by and added more details to > description > > This bug appeared in the original submission (v3.5) Patch applied. However your patch was totally white-space damaged. I've fixed it this time, but please fix this in your future submissions. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/