Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp3063958pxb; Sat, 6 Feb 2021 18:49:11 -0800 (PST) X-Google-Smtp-Source: ABdhPJyUSM0i71Zu3V1kSziae4KgrAyxzu4RwtofouQq2RUhXgucll1RQX7s1NwNxBSqwHbOupNm X-Received: by 2002:a05:6402:104b:: with SMTP id e11mr7585063edu.367.1612666151315; Sat, 06 Feb 2021 18:49:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612666151; cv=none; d=google.com; s=arc-20160816; b=YQf5Cw0QXAi5AcbaaiDv25xJZF7HGAN/bg94u7Tci7jKIu9iqt+KFq4tQmdfyI093K 4Qd1vfU9fqIP90O6OcmkEdOMGJp+CP29LPjPnbYiJZZbwroZhW6K/ebt6r7DIECjVGy4 9FVmh5ezT99pi/uGnqA9sQrIwMXurP2mRF7F465U2Zo5Nj48W41i0onzVC9OKzl6M0q9 L7RxEm1eEiKF8W+ajOoKnMi5H98ZLzPsmK6fR303zqtWzgyo7y3DKjHApRyso39rVUNB HkGdYV92HjqfE7j7YYWog41ur4t29FyxY/HNqGfbZXMLqY5TF8+GZCTO4s84TNw5Munj ObAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=MmuSMzpsdxcUGaAdXACLYAd+o9HwWdtJufg6P0alBJw=; b=N+/DftsxBmRA1fkWBLotpunONerUG4iebZb1o11ChW0uo7Ayj84usYyTaHqGm9sMM6 Sc8sIxpP9T66nYm16gd2wHh06HnWD8lIv3a1EiFUSZSCLEZXM+F+qdV7LOhoDyJt6/CJ APGCy29gihp2lsKW1UuUPzq92BnVwEEEqCofPdEyI+poUcfyPVuCcMEFm72zbcl7sctD gWGNZiXdpkmKvttxNAGnMs9fJEaxR1JgJi607IRQIMF5owhkH9gvPq7y7WTM2XCPZwnr aPK5ytSehht6mrdT7is6qU5ttDV2OoVh4vn+Yl9QUbQpdO+dmeNt6Wvr96zInuMOJiSo B4gw== 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 l17si7961711ejf.260.2021.02.06.18.48.46; Sat, 06 Feb 2021 18:49:11 -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 S229529AbhBGCrn (ORCPT + 99 others); Sat, 6 Feb 2021 21:47:43 -0500 Received: from szxga04-in.huawei.com ([45.249.212.190]:11687 "EHLO szxga04-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229506AbhBGCrn (ORCPT ); Sat, 6 Feb 2021 21:47:43 -0500 Received: from DGGEMS403-HUB.china.huawei.com (unknown [172.30.72.59]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4DYD654X70zlD5s; Sun, 7 Feb 2021 10:45:17 +0800 (CST) Received: from [10.67.102.118] (10.67.102.118) by DGGEMS403-HUB.china.huawei.com (10.3.19.203) with Microsoft SMTP Server id 14.3.498.0; Sun, 7 Feb 2021 10:46:50 +0800 Subject: Re: [PATCH 3/3] crypto: hisilicon/sec - fixes shash test error To: Herbert Xu CC: , , , , "Ard Biesheuvel" References: <1612519857-30714-1-git-send-email-liulongfang@huawei.com> <1612519857-30714-4-git-send-email-liulongfang@huawei.com> <20210205114435.GA17031@gondor.apana.org.au> From: liulongfang Message-ID: <70c0e041-9bcc-aa67-a0ad-a1a202f2e708@huawei.com> Date: Sun, 7 Feb 2021 10:46:50 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20210205114435.GA17031@gondor.apana.org.au> Content-Type: text/plain; charset="gbk" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.102.118] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On 2021/2/5 19:44, Herbert Xu write: > On Fri, Feb 05, 2021 at 06:10:57PM +0800, Longfang Liu wrote: >> If this configuration item is not turned on, >> the allocation of crypto_tfm will fail when >> the shash algorithm calculates the hash >> through the software. >> >> Signed-off-by: Longfang Liu >> --- >> arch/arm64/configs/defconfig | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig >> index 8383016..7cfc9b6 100644 >> --- a/arch/arm64/configs/defconfig >> +++ b/arch/arm64/configs/defconfig >> @@ -117,7 +117,7 @@ CONFIG_KVM=y >> CONFIG_ARM64_CRYPTO=y >> CONFIG_CRYPTO_SHA1_ARM64_CE=y >> CONFIG_CRYPTO_SHA2_ARM64_CE=y >> -CONFIG_CRYPTO_SHA512_ARM64_CE=m >> +CONFIG_CRYPTO_SHA512_ARM64_CE=y > > If this is truly needed then it should be enabled through Kconfig. > > Cheers, > Hi Herbert, The option select CRYPTO_SHA512 already exists in Kconfig. Can I change it to this: select CRYPTO_SHA512 || CRYPTO_SHA512_ARM64_CE Thanks, Longfang Liu.