Thread (14 messages) 14 messages, 3 authors, 2017-12-22

[PATCH RFC 1/4] crypto: engine - Permit to enqueue all async requests

From: clabbe.montjoie@gmail.com (Corentin Labbe)
Date: 2017-12-22 08:41:56
Also in: linux-crypto, lkml

On Fri, Dec 22, 2017 at 05:57:24PM +1100, Herbert Xu wrote:
On Wed, Nov 29, 2017 at 09:41:18AM +0100, Corentin Labbe wrote:
quoted
The crypto engine could actually only enqueue hash and ablkcipher request.
This patch permit it to enqueue any type of crypto_async_request.

Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
This is going the wrong way.  We do not want to expose any of the
base types such as crypto_alg, crypto_async_request to end-users
and that includes drivers.  Only core API code should touch these
base types.
Hello

It's you that was suggesting using crypto_async_request:
https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1474434.html
"The only wart with this scheme is that the drivers end up seeing
struct crypto_async_request and will need to convert that to the
respective request types but I couldn't really find a better way."

So I wait for any suggestion.

Regards
Corentin Labbe
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help