From: Herbert Xu Subject: Re: Remaining crypto API regressions with CONFIG_VMAP_STACK Date: Tue, 13 Dec 2016 11:39:42 +0800 Message-ID: <20161213033942.GC5601@gondor.apana.org.au> References: <20161209230851.GB64048@google.com> <1747e6e9-35dc-48cc-7345-4f0412ba2521@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andy Lutomirski , Eric Biggers , linux-crypto@vger.kernel.org, "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "kernel-hardening@lists.openwall.com" , Andrew Lutomirski , Stephan Mueller To: Gary R Hook Return-path: Content-Disposition: inline In-Reply-To: <1747e6e9-35dc-48cc-7345-4f0412ba2521@amd.com> Sender: owner-linux-mm@kvack.org List-Id: linux-crypto.vger.kernel.org On Mon, Dec 12, 2016 at 12:45:18PM -0600, Gary R Hook wrote: > On 12/12/2016 12:34 PM, Andy Lutomirski wrote: > > <...snip...> > > > > >I have a patch to make these depend on !VMAP_STACK. > > > >> drivers/crypto/ccp/ccp-crypto-aes-cmac.c:105,119,142 > >> drivers/crypto/ccp/ccp-crypto-sha.c:95,109,124 > >> drivers/crypto/ccp/ccp-crypto-aes-xts.c:162 > >> drivers/crypto/ccp/ccp-crypto-aes.c:94 > > > >According to Herbert, these are fine. I'm personally less convinced > >since I'm very confused as to what "async" means in the crypto code, > >but I'm going to leave these alone. > > I went back through the code, and AFAICT every argument to sg_init_one() in > the above-cited files is a buffer that is part of the request context. Which > is allocated by the crypto framework, and therefore will never be on the > stack. > Right? Right. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org