Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp4563633rwb; Tue, 8 Nov 2022 19:56:07 -0800 (PST) X-Google-Smtp-Source: AMsMyM4vVU4LVG5tUZklpmcx3kG9KPKVlYSYoSsK+uFstwJcAAXKLcACZ9BNXoXAtdI7yJx16fjO X-Received: by 2002:a17:907:a4c:b0:77b:ba98:d3e with SMTP id be12-20020a1709070a4c00b0077bba980d3emr56578561ejc.13.1667966167412; Tue, 08 Nov 2022 19:56:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1667966167; cv=none; d=google.com; s=arc-20160816; b=xlcTz73++JtRq3PMUlnIzi2ZdGZAD5ISooeT1TJb3PmFtgYSVQ8WgTiduq2OeKOfDY /ReCMaSqmr8upruqZlP0ULX0u1J9NgR2HhVUbXiaLyFOk9hkw03VREWRQFBtCSama63z ayK75r5bje/kHLBRRQ0Ou+MD7IY/8P2RonivuxxQFVl3h9MGi2+N88R8/Oaug4Bw4Y/C WC5XtUFcQYeC6diaYw1W3pCKTRIWBQD9nqsPhhP9vC2prtneQw+mOx2YeQINhCEmNvTm +SvkNQy4lOIABb4z5GM6GtPW8P5jVnnaWolI2u9g1IBFz18Pb1jUAxkAYJcTjTjyAGcd AZ7Q== 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=s4UH/opcfxzD53i7Ftk5fbaHym6YjMCMZ9lXMrt3f2k=; b=Nwff4XVROBO+L28BYG0f6NmfLrqMtjsFBfWWMnKTwTAcElzghm2Bj259s3VWMwu64X f6B0i//HY31a8DhLZezWUtJ+Axt4A8NCo+Q9QjYdxbrX+Z155cqmzN+VBKHT0D+QDa4q 1IP1OB1Bu04oKPHCCmskaVrvCBmchUTxedJiNVAp4WWVpJJXR8W290ar+axLvN8Vubz5 Cj9Xx+X/qQh4jb9caYXeS4UnF4X94I5ypfkMx20XspyKkt4WM+evfjPkYRDMjL1g2jgj pvuFLAY+NP/s+etZmsdDV9z+/kRWYl9NjxuD9+aVjBTnMcaY+xoFJbmnzFSFbpXD2q4w A0/w== 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 b9-20020aa7cd09000000b0045da52f303csi12148907edw.213.2022.11.08.19.55.29; Tue, 08 Nov 2022 19:56:07 -0800 (PST) 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 S229624AbiKIDwZ (ORCPT + 99 others); Tue, 8 Nov 2022 22:52:25 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37064 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229553AbiKIDwY (ORCPT ); Tue, 8 Nov 2022 22:52:24 -0500 Received: from formenos.hmeau.com (helcar.hmeau.com [216.24.177.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 326A2165AE for ; Tue, 8 Nov 2022 19:52:22 -0800 (PST) Received: from loth.rohan.me.apana.org.au ([192.168.167.2]) by formenos.hmeau.com with smtp (Exim 4.94.2 #2 (Debian)) id 1osc7q-00BoUK-Va; Wed, 09 Nov 2022 11:52:20 +0800 Received: by loth.rohan.me.apana.org.au (sSMTP sendmail emulation); Wed, 09 Nov 2022 11:52:19 +0800 Date: Wed, 9 Nov 2022 11:52:19 +0800 From: Herbert Xu To: Ben Greear Cc: Ard Biesheuvel , Linux Crypto Mailing List , Eric Biggers Subject: Re: [PATCH v2] crypto: aesni - add ccm(aes) algorithm implementation Message-ID: References: <20201210024342.GA26428@gondor.apana.org.au> <20201210111427.GA28014@gondor.apana.org.au> <20201210121627.GB28441@gondor.apana.org.au> <20201215091902.GA21455@gondor.apana.org.au> <062a2258-fad4-2c6f-0054-b0f41786ff85@candelatech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <062a2258-fad4-2c6f-0054-b0f41786ff85@candelatech.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 Tue, Nov 08, 2022 at 10:50:48AM -0800, Ben Greear wrote: > > While rebasing my patches onto 6.1-rc4, I noticed my aesni for ccm(aes) patch didn't apply cleanly, > and I found this patch described below is applied now. Does this upstream patch mean that aesni is already > supported upstream now? Or is it specific to whatever xctr is? If so, > any chance the patch is wanted upstream now? AFAICS the xctr patch has nothing to do with what you were trying to achieve with wireless. My objection still stands with regards to wireless, we should patch wireless to use the async crypto interface and not hack around it in the Crypto API. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt