From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BC5FE1F5FA; Sat, 18 May 2024 13:03:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716037411; cv=none; b=QNaTRmb7uVEOM2cRfDySnPHVuNaCgvO1n7R+KoLbAI2QxpVbzuDpmiDqR0yoldsjPkZY9o2Yw76GarSwl0vFUz1uwqfT9NahM4JbveQtId5m5sgy+prTIpjUy6atGnOIUPCCcUdAyZbh8RTQx90U7parPleeAxydly9GP/ZxJ+o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716037411; c=relaxed/simple; bh=ZggJadfHy1NOHs7+8mfVbZ9wI8BBKNLewZn820T/SN0=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:Subject:From:To: References:In-Reply-To; b=iHOuLYY87VvlqcDf20sBR1N/D0YYZi9Lf/cP8QwCGZwY6pfVpx2eGbjXG4lV+OaqCwEP7pUlryfyAz9edan7hUMw61aWX5gnpJ+FmnHfPmWvDhSIbqNMNUOtSsPO2L4OcQ0Os3baBTqFu6F7fLFfUxvfIItfcnT7SnFtxcO/coQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Zuel/urP; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Zuel/urP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 064DDC113CC; Sat, 18 May 2024 13:03:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1716037410; bh=ZggJadfHy1NOHs7+8mfVbZ9wI8BBKNLewZn820T/SN0=; h=Date:Cc:Subject:From:To:References:In-Reply-To:From; b=Zuel/urP9lpCRixHrKBB4PYNBACOVkPvR9+8Qwmt3+OOrUG+AzLlTcksw12tb9GHg G/iFqH3SOIFw0gdvQ8wm3/d0lVYfD4yNl/JEsZtUl7TGAXMMdYuyDncVYqONDEJdyz 2U7yXw90iJsCdLKf4Cr//qp8+xCBfHfnpx7fUp7lJTOpsc49nsNyrieV2BvngDvdoG F8qoGFwXw66UKmXD+sXUrMdkq1oj0YC5+u4YlLt4i/CegOf5eFuI+eyYvY8qRZiMJf eMSCcGCIT0zIGP1BlW7wrCX2+BnKNhtNKAEfP4eVkqujaqX5/WQE8vwdSNdN8TeNU3 3z2bq5/tMGcWQ== Precedence: bulk X-Mailing-List: linux-integrity@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Sat, 18 May 2024 16:03:26 +0300 Message-Id: Cc: "Eric Biggers" , =?utf-8?b?TsOtY29sYXMgRi4gUi4gQS4gUHJhZG8=?= , "James Bottomley" , "Ard Biesheuvel" , "Linux Crypto Mailing List" , , , , Subject: Re: [PATCH] crypto: api - Do not load modules until algapi is ready From: "Jarkko Sakkinen" To: "Herbert Xu" X-Mailer: aerc 0.17.0 References: <0f68c283ff4bbb89b8a019d47891f798c6fff287.camel@HansenPartnership.com> <0d260c2f7a9f67ec8bd2305919636678d06000d1.camel@HansenPartnership.com> <66ec985f3ee229135bf748f1b0874d5367a74d7f.camel@HansenPartnership.com> <20240518043115.GA53815@sol.localdomain> In-Reply-To: On Sat May 18, 2024 at 3:32 PM EEST, Herbert Xu wrote: > On Sat, May 18, 2024 at 02:04:18PM +0300, Jarkko Sakkinen wrote: > > > > Right does this mean for TPM driver that a crypto API invocation not > > having everthing needed loaded will block until this is not the case? > > All this does is disable module loading by the Crypto API (because > there is no point and it may deadlock) until such a point where > all/most drivers have finished loading. > > So if the algorithm is missing (which shouldn't happen because of > Kconfig selects), then it will simply fail. > > Cheers, Ok, you can add Reviewed-by: Jarkko Sakkinen BR, Jarkko