Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4010912ybb; Mon, 6 Apr 2020 21:59:34 -0700 (PDT) X-Google-Smtp-Source: APiQypKS2NkIbQVz5JoG/W+Tmptr6SgA5LFdudagUkccJKEcohx53LsrUO8QoymT3ymalMhP2vPJ X-Received: by 2002:a4a:9c86:: with SMTP id z6mr489035ooj.68.1586235574418; Mon, 06 Apr 2020 21:59:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586235574; cv=none; d=google.com; s=arc-20160816; b=LB0udnyCPppC0ICQZr2XKMoKTcrYqn/12GXqqfHYlIhRNX/TS9vUI0Fi91Nh1pRyMy 3spc0m0Dvo3MH2QLrvyx+ZyO4wgjfmEKiWvTHCeyLpczHhT2hMBAWh4Z/9UT518A3POb j2U8h/BbRoIol0gcospvGeMufDOx4rXQM6FPGRQyhjkkH3oF0ae1v3Xa8WkCm0KmMuI8 PgcRgM2J4k5d26Pf//YWqJatXOkCwLArJghfmN3DxMGRFqAq7DVwc8nXs0G7fgQUO3pq e0zPRkkS7FqK+ddX5L+nbb2/02jMKgp1WkvQ6z0ZogOQz4zmuC6xcUw+SrWdUcYlpyAa zijQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=ECmUgLyzA18r9Sfn/O+YQ2+0vQ2TGzPhOW5WHuoE+Qw=; b=pNT7kVJ2kZvbEHlB/fZ9eqAo4STK4SHA2XmUZ/8Lbb4R0VcU+keiOLk/UQ1r8XP3Bi HyXMha+JIzi7UvNXgs4TfF1ZUIQaixQ+cI7BG4bnRk6kfzEhP5m+Eq1Y+MaoH7/PvLtp qEW1cZRBthxlSHM4QzqVGSLMisKUJ5QDNnNn3xTbR50zT4rCeAmUuMQhYHWYfIxBBNe5 0yobCSZ5ReklTYoYMZ82mouv/IJertUqwVb+r4um8T8E+AEdbD/5A6J9CUWkZ85dosl8 REUunPkNlolY7EbSN9njHElluKaFpdLaqe3SOa/JgMrrOVFNp6kL7q71UyxrbHncxWkk +Bcg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=MRqJTyxi; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z78si197451oia.200.2020.04.06.21.59.10; Mon, 06 Apr 2020 21:59:34 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=MRqJTyxi; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725883AbgDGE6i (ORCPT + 99 others); Tue, 7 Apr 2020 00:58:38 -0400 Received: from mail.kernel.org ([198.145.29.99]:39392 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726030AbgDGE6i (ORCPT ); Tue, 7 Apr 2020 00:58:38 -0400 Received: from sol.localdomain (c-107-3-166-239.hsd1.ca.comcast.net [107.3.166.239]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 680BB206BE; Tue, 7 Apr 2020 04:58:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1586235517; bh=r91KxDKQs7nxeFamX6w+PiN3ptOt9aVDPR9VN1EabDA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=MRqJTyxiMJ+05naBx89XSeDwh4lmJVRQEZUCcJEa6S8KWz3rZ+6kzgxhqct5bBY1s mNPtV5s5VRPSCyHpdpwOAhXMEUJfhOCs9KmHg9Yf/mGfY1gnaQLR6ea2PLQp5GTR9E JIMODJDLJIOV8OHCL+3ObUUeDvkk3WuMqmkm/X8s= Date: Mon, 6 Apr 2020 21:58:35 -0700 From: Eric Biggers To: Herbert Xu Cc: Linux Crypto Mailing List Subject: Re: crypto: algboss - Avoid spurious modprobe on LOADED Message-ID: <20200407045835.GA102437@sol.localdomain> References: <20200407030003.GA12687@gondor.apana.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200407030003.GA12687@gondor.apana.org.au> Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Tue, Apr 07, 2020 at 01:00:03PM +1000, Herbert Xu wrote: > As it stands when any algorithm finishes testing a notification > is generated which triggers an unnecessary modprobe because algboss > returns NOTIFY_DONE instead of NOTIFY_OK (this denotes an event > that is not handled properly). > > This patch changes the return value in algboss so that we don't > do an unnecessary modprobe. > > Signed-off-by: Herbert Xu Needs a Fixes tag? Fixes: dd8b083f9a5e ("crypto: api - Introduce notifier for new crypto algorithms") Cc: # v4.20+ > > diff --git a/crypto/algboss.c b/crypto/algboss.c > index 527b44d0af21..01feb8234053 100644 > --- a/crypto/algboss.c > +++ b/crypto/algboss.c > @@ -275,7 +275,7 @@ static int cryptomgr_notify(struct notifier_block *this, unsigned long msg, > case CRYPTO_MSG_ALG_REGISTER: > return cryptomgr_schedule_test(data); > case CRYPTO_MSG_ALG_LOADED: > - break; > + return NOTIFY_OK; > } > > return NOTIFY_DONE; It's hard to remember the difference between NOTIFY_OK and NOTIFY_DONE. Isn't it wrong to call request_module() in the first place for a message that "cryptomgr" doesn't care about? Wouldn't the following make more sense?: diff --git a/crypto/algapi.c b/crypto/algapi.c index 69605e21af92..849254d7e627 100644 --- a/crypto/algapi.c +++ b/crypto/algapi.c @@ -403,7 +403,7 @@ static void crypto_wait_for_test(struct crypto_larval *larval) err = wait_for_completion_killable(&larval->completion); WARN_ON(err); if (!err) - crypto_probing_notify(CRYPTO_MSG_ALG_LOADED, larval); + crypto_notify(CRYPTO_MSG_ALG_LOADED, larval); out: crypto_larval_kill(&larval->alg);