From: Tadeusz Struk Subject: Re: [crypto / sparc64] cryptomgr_test OOPS Date: Thu, 5 May 2016 09:17:32 -0700 Message-ID: References: <20160503.123301.298039059390449291.davem@davemloft.net> <20160504040731.GA25758@gondor.apana.org.au> <20160505084249.GA4971@gondor.apana.org.au> <20160505095020.GA5473@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: David Miller , linux-crypto@vger.kernel.org, sparclinux@vger.kernel.org, Nicolai Stange To: Herbert Xu , Anatoly Pugachev Return-path: In-Reply-To: <20160505095020.GA5473@gondor.apana.org.au> Sender: sparclinux-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On 05/05/2016 02:50 AM, Herbert Xu wrote: > On Thu, May 05, 2016 at 12:40:18PM +0300, Anatoly Pugachev wrote: >> >> sure, based on your cryptodev git, just tried 4.3 (6a13feb , good) >> kernel in attempt to find (bisect) when RSA code break, already tested >> 4.5 (44d1b6d , bad) , 4.4 (afd2ff9 , bad). >> Going to try your patch soon (when I'm back home). >> So far 4.3 passes RSA stage without OOPS, but for other reason does >> not boot to login prompt. Boot log exempt (4.3), this is with >> CONFIG_CRYPTO_RSA=y : > > That jibes with this being a problem with the SG list since it > was only added in 4.4. Before 4.4 the rsa sw implementation kmalloced intermediate flat buffer and copied the data internally. Thanks, -- TS