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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CD6E2C433EF for ; Fri, 5 Nov 2021 14:33:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id ACD5661186 for ; Fri, 5 Nov 2021 14:33:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233255AbhKEOgQ (ORCPT ); Fri, 5 Nov 2021 10:36:16 -0400 Received: from new1-smtp.messagingengine.com ([66.111.4.221]:51865 "EHLO new1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233230AbhKEOgP (ORCPT ); Fri, 5 Nov 2021 10:36:15 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id D3718580873; Fri, 5 Nov 2021 10:33:34 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 05 Nov 2021 10:33:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=7vHGH5 fsWp+AmiltcS8fSgzVtFKPV6KtppB0gEokIww=; b=ZtwKF4f/OZwYUAfoIxksjl eLsbDweOswOJhxqMcdKfCjt6sk0ObD3uMVNPUP7lRF/vwbmmhKs/Ddy5h2YtGITO uW+evRjVm7z6TkBwiZKzXb8GrRW8kJe0sQVuIgJwUpq6YrZw8MvQkkW3rThe+Vv6 BEZvElSUfG61SmwPvtoND+ICMSA5Ac2VrrZgGkV7Du6cdlbbhdo92AdMnp6aw5zc u9xyQ4iTuHSAiC6UdCuzLsuZHr8Kgtbqx3vdiFRKEFNJMryF7LDYyxA93vpJwlLh Gdw3mDSEtxHUGdRMJvX63R5YxGpfmzxzLKGvFLF1yci26Xkd9sUbDvKlpXBNDWYA == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrtdeigdeigecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtrodttddtvdenucfhrhhomhepkfguohcuufgt hhhimhhmvghluceoihguohhstghhsehiughoshgthhdrohhrgheqnecuggftrfgrthhtvg hrnhepgfejvefhvdegiedukeetudevgeeujeefffeffeetkeekueeuheejudeltdejuedu necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepihguoh hstghhsehiughoshgthhdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 5 Nov 2021 10:33:32 -0400 (EDT) Date: Fri, 5 Nov 2021 16:33:29 +0200 From: Ido Schimmel To: Herbert Xu Cc: Geert Uytterhoeven , Damien Le Moal , Nathan Chancellor , Linux Crypto Mailing List , Vladis Dronov , Simo Sorce , Eric Biggers , "llvm@lists.linux.dev" , kernel test robot , "linux-kernel@vger.kernel.org" , Guenter Roeck Subject: Re: crypto: api - Fix boot-up crash when crypto manager is disabled Message-ID: References: <20211019132802.GA14233@gondor.apana.org.au> <20211104121612.GA8044@gondor.apana.org.au> <20211104133044.GA8563@gondor.apana.org.au> <20211105072608.GA13584@gondor.apana.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211105072608.GA13584@gondor.apana.org.au> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 05, 2021 at 03:26:08PM +0800, Herbert Xu wrote: > On Thu, Nov 04, 2021 at 05:18:34PM +0200, Ido Schimmel wrote: > > > > Attached my config. I can easily test patches. > > Thanks! > > Could you all try this patch please? > > ---8<--- > When the crypto manager is disabled, we need to explicitly set > the crypto algorithms' tested status so that they can be used. > > Fixes: cad439fc040e ("crypto: api - Do not create test larvals if...") > Reported-by: Geert Uytterhoeven > Reported-by: Ido Schimmel > Reported-by: Guenter Roeck > Signed-off-by: Herbert Xu Tested-by: Ido Schimmel Thanks, Herbert!