From: Herbert Xu Subject: Re: Doing crypto in small stack buffers (bluetooth vs vmalloc-stack crash, etc) Date: Wed, 22 Jun 2016 08:42:14 +0800 Message-ID: <20160622004214.GA27134@gondor.apana.org.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Johan Hedberg , Gustavo Padovan , Marcel Holtmann , linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "David S. Miller" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Linus Torvalds To: Andy Lutomirski Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-bluetooth-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-crypto.vger.kernel.org On Tue, Jun 21, 2016 at 10:43:40AM -0700, Andy Lutomirski wrote: > > Is there a straightforward way that bluetooth and, potentially, other > drivers can just do synchronous crypto in a small buffer specified by > its virtual address? The actual cryptography part of the crypto code > already works this way, but I can't find an API for it. Yes, single block users should use crypto_cipher_encrypt_one, an example would be drivers/md/dm-crypt.c. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt