Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030369Ab3HIGaO (ORCPT ); Fri, 9 Aug 2013 02:30:14 -0400 Received: from ringil.hengli.com.au ([178.18.16.133]:39039 "EHLO fornost.hengli.com.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1030220Ab3HIGaM (ORCPT ); Fri, 9 Aug 2013 02:30:12 -0400 Date: Fri, 9 Aug 2013 16:30:03 +1000 From: Herbert Xu To: Benjamin Herrenschmidt Cc: Fionnuala Gunter , 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: <20130809063003.GB23506@gondor.apana.org.au> References: <1375917350.16050.14.camel@what-is-leg> <1376029504.32100.16.camel@pasglop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1376029504.32100.16.camel@pasglop> 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: 1088 Lines: 26 On Fri, Aug 09, 2013 at 04:25:04PM +1000, Benjamin Herrenschmidt wrote: > On Wed, 2013-08-07 at 18:15 -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 > > Herbert, I assume you will handle this along with all the other NX fixes > and I can safely take them out of linuxppc patchwork ? Yes of course. Thanks, -- 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/