Received: by 2002:ac0:e34a:0:0:0:0:0 with SMTP id g10csp347858imn; Thu, 28 Jul 2022 02:30:46 -0700 (PDT) X-Google-Smtp-Source: AGRyM1sEGRH6g5790Y4OQE0ivGkHn+FoGK5Pye009+7YekbeiTyyFyd++mT+E6nzbNqC8tLgCp/w X-Received: by 2002:a17:907:d0f:b0:72e:db1f:9b91 with SMTP id gn15-20020a1709070d0f00b0072edb1f9b91mr20900945ejc.470.1659000646157; Thu, 28 Jul 2022 02:30:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659000646; cv=none; d=google.com; s=arc-20160816; b=yaROa10ciZ3m0YFHXIpCkgWcpfZH3RRfh2mx5FaEJ2l3/UGXuAPZJayINK3877Mc5E vArD3RKhyK/76JnIo6FlEhSSul0xSn7A/RNUfWj3O/SSpebumTfLeXysCk68VW9WEX/r ZwKlfHlttLCmaydacKx5WCoP51KBBd4niSgY+kLiXHfKQxDJ9VezfvjJCGY3QX1c3wCu PNnpFZcl9CXJfuTBuQqDgHi0htoPSIh2tTo1MxmZ54SagtI9wP0MAWbhcVu126xlt/pX 61sh1R7oyLE54oVV0JtwBhnqjNBXO5GopazySP0L8zfkeV2nNt3FKEhOkqd4jEwQICpM qX/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=0tRwGW1TsdWqk3mWbmOH4sLShjNUm0/DyxfONDmDz7g=; b=i0Tm6r36t/v7fKvcVe20RpmKx36pOw1hmKcWm3WeuZdO9pgfJ20NlXZuZ/mcRf/eIx 7EmiZkWfEq+dNMFyqLCg2/Nu7XiMvvvwqBeDxuvZBUvIRBtv6VylIyUi9cW8Y59IqWO7 M8DIUt+DlCBjy2i2UeMISnIRtWNh536IgNtXekqiUP83jE1UAsjwN9qI/Xuomth2u+zT QlLPAoIKH5X7Q5zP9/hdFJhRSVyum/mwfLtTJo8ieGHxVUS/uyXTc5XkpW0HQwv0UirB /RzPoWtOytzkb0I1IfIFywFeLyPNxG/SniBHzoXzyrWK5RTskmqo3coco/rzKE3LuDjg 3Qlg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ti5-20020a170907c20500b0072b8cd4ca77si239597ejc.274.2022.07.28.02.30.11; Thu, 28 Jul 2022 02:30:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235486AbiG1J0h (ORCPT + 99 others); Thu, 28 Jul 2022 05:26:37 -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> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@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