From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 29F56C04A68 for ; Thu, 28 Jul 2022 09:26:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235508AbiG1J0i (ORCPT ); Thu, 28 Jul 2022 05:26:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35352 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234953AbiG1J0g (ORCPT ); Thu, 28 Jul 2022 05:26:36 -0400 Received: from fornost.hmeau.com (helcar.hmeau.com [216.24.177.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2682F65825; Thu, 28 Jul 2022 02:26:33 -0700 (PDT) Received: from gwarestrin.arnor.me.apana.org.au ([192.168.103.7]) by fornost.hmeau.com with smtp (Exim 4.94.2 #2 (Debian)) id 1oGzmX-005Ou3-Pj; Thu, 28 Jul 2022 19:26:15 +1000 Received: by gwarestrin.arnor.me.apana.org.au (sSMTP sendmail emulation); Thu, 28 Jul 2022 17:26:14 +0800 Date: Thu, 28 Jul 2022 17:26:14 +0800 From: Herbert Xu To: Leonard Crestez Cc: Dmitry Safonov , linux-kernel@vger.kernel.org, Dmitry Safonov <0x7f454c46@gmail.com>, Andy Lutomirski , Ard Biesheuvel , David Ahern , "David S. Miller" , Eric Biggers , Eric Dumazet , Francesco Ruggeri , Hideaki YOSHIFUJI , Jakub Kicinski , Paolo Abeni , Salam Noureddine , netdev@vger.kernel.org, linux-crypto@vger.kernel.org Subject: Re: [PATCH 0/6] net/crypto: Introduce crypto_pool Message-ID: References: <20220726201600.1715505-1-dima@arista.com> <5b88eea6-1d84-8c16-36f4-358053e247f2@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5b88eea6-1d84-8c16-36f4-358053e247f2@gmail.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 27, 2022 at 06:52:27PM +0300, Leonard Crestez wrote: > > The fact that setkey is implemented at the crypto_ahash instead of the > ahash_request level is baked into all algorithm implementations (including > many hardware-specific ones). Changing this seems extremely difficult. What I had in mind is simply making the tfm setkey optional. That way you could then have an additional setkey at the request level. If the key is provided in either place you're allowed to perform the hash. This should have minimal impact on existing code. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt