Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp6922005pxb; Wed, 17 Feb 2021 18:08:41 -0800 (PST) X-Google-Smtp-Source: ABdhPJyvADtoNRhRxVKXrC94cT8iL4TEL25dCHTUixltQzc5zSRDRLURRzJOtGA2VAfLa7HwBuer X-Received: by 2002:a17:906:4b02:: with SMTP id y2mr1673995eju.475.1613614121433; Wed, 17 Feb 2021 18:08:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613614121; cv=none; d=google.com; s=arc-20160816; b=fQaO/Nw+gavv1dFCLKhutjvDZu3qA+UWRJs0vsYTnevMBMghqlN1LdmxDh1r17uxVP GlnQ1ytIzokyVmcWLvyKryMK8SeOjAqNatC4yIAFqSy2WicAi9UYd46NJlIOQSwDvZxZ UIU3xaveIrS8s92fY7SM6IQDThyh/65pAKrosxwhcaF4W52dJkMnlPLTYgmrrnaU2reE iEsBELnxFNxP64d6g00VKEd7lyoF1kc0yIShAsd2UMGkXEYk6HhAjd3CMYJXmVdI7/bl wX5v47BpnVFQK8cOUYudW3HmdX0OZGuqEtmtPwFniSOHD8bNUpw1HpXloN7Q1rlkds1q NDXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=wn30m4gW/k5h0SP3129PBqWLU6gkRY8IdX4KrVgreXg=; b=MT+SplV59UgoHzzfWzsxxYpaGkw2mwREfKMDVCXHT/u5/Kiqmb7qTHVKTLR52HX6wW HjuUh6bmnYnNhk5eBQN3d9o8SxpCLg+qMxPMCOHiVeZI6XD+CKy7HFdOkfpsR+PtAaS+ gHnCkrnB/o5hNWqrvt+OSGiZxmlEGkM81SI8eBXjPEsixwFsQOhqKmQ15N62CWBSDO9I WJ850Eo6FrZ2StnCBmACtcx+OlQY90dQzvODs+lvb02BF4VOpsQSAPEOIixIuDLeHJX2 BleNZsTXX9mx4vgehPEO1qPNuazPreJQb5yYIsePOPb0daq3pc+uzoNoFlaMn1MJI9mJ /WDQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c24si2511267edv.48.2021.02.17.18.08.16; Wed, 17 Feb 2021 18:08:41 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229874AbhBRCHt (ORCPT + 99 others); Wed, 17 Feb 2021 21:07:49 -0500 Received: from helcar.hmeau.com ([216.24.177.18]:34530 "EHLO fornost.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229806AbhBRCHt (ORCPT ); Wed, 17 Feb 2021 21:07:49 -0500 Received: from gwarestrin.arnor.me.apana.org.au ([192.168.103.7]) by fornost.hmeau.com with smtp (Exim 4.92 #5 (Debian)) id 1lCYiN-0006Z3-Cy; Thu, 18 Feb 2021 13:06:48 +1100 Received: by gwarestrin.arnor.me.apana.org.au (sSMTP sendmail emulation); Thu, 18 Feb 2021 13:06:47 +1100 Date: Thu, 18 Feb 2021 13:06:47 +1100 From: Herbert Xu To: liulongfang Cc: wangzhou1@hisilicon.com, xuzaibo@huawei.com, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 3/3] crypto: hisilicon/sec - fixes shash test error Message-ID: <20210218020647.GB30659@gondor.apana.org.au> References: <1612692280-11386-1-git-send-email-liulongfang@huawei.com> <1612692280-11386-4-git-send-email-liulongfang@huawei.com> <20210210064328.GA15849@gondor.apana.org.au> <0afaed85-eeb0-236c-817f-a0f9cf02c65a@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0afaed85-eeb0-236c-817f-a0f9cf02c65a@huawei.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Thu, Feb 18, 2021 at 10:01:58AM +0800, liulongfang wrote: > > >> diff --git a/drivers/crypto/hisilicon/sec2/sec_crypto.c b/drivers/crypto/hisilicon/sec2/sec_crypto.c > >> index d2c4a2c..988faf7 100644 > >> --- a/drivers/crypto/hisilicon/sec2/sec_crypto.c > >> +++ b/drivers/crypto/hisilicon/sec2/sec_crypto.c > >> @@ -7,6 +7,7 @@ > >> #include > >> #include > >> #include > >> +#include > > > > Please explain what exactly in this file needs this header file. > > > > As it stands you could just be hiding real bugs. > > > > Thanks, > > > The crypto_alloc_shash() interface in the header file > will be used in the function sec_aead_ctx_init(), > If this header file is not added, calling the interface > crypto_alloc_shash() during the initialization of the > aead algorithm will return an error. This makes no sense whatsoever as crypto_alloc_shash is defiend by crypto/hash.h and you've already included that. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt