Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp196472ybm; Wed, 27 May 2020 23:58:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzvQ87mGH15OH254BslVtNgft7UdkEomhlnNivM1F7t5IAdqTgcaDHF5X+/r0efpJGqmd3y X-Received: by 2002:a50:e808:: with SMTP id e8mr1687846edn.258.1590649139713; Wed, 27 May 2020 23:58:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590649139; cv=none; d=google.com; s=arc-20160816; b=LN1JuZl4AEzPifon5fMUc5YIH6Jid7ZGh/yLI9tzP8LYo8/HAtMBdtn0pcfcXqxSiI FqW2tuBvimWBAAGbNzGHpZDiIZlk/bGpNmpmfKRxcvP7eaGADoQGifP/Wf6hMvrGeOmt FGO4QE5aUH36IfvgC5pPEFW9vJxOkCxtpW602P+jKuYgllcy04Mfz6V8o68oPxGPoAUw bBgoS/9CBs/aF+0ZskwMTfQkr4nRGAu+X5/grYBrHFHQx5vYB7te3bVLBsXSB75J47CS tQoH/+7uW9S1VBXJGVXJSFQ/GGe/i5J3jWkGYa+4uACvDs1eOQ9hTVembAluybgHM9wt NHEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=tm90awzHhPtDUz+mQ7UE3flOmrtwmQA7XVARLpRl00w=; b=nSZ2gBnr8fmUQBuw/5XqxSseEHSu2M6foVxrLh0fsaTcb517op9/nkgkOPDjcSSEcR bBu0kMQUM0Qwdyvhh6SwHm1TC+zMx9/Dx9U5DkoFM8wJnenjCdxecencrI+27ecq/7Z/ ahesoD39Dh6vnr6rhUgunyLa7p3UiRTVPnv+iSmEg4PPQFx7PO6hO6fVWQ/lNBy5H0gO uoWF3gQEqh7xKqPhdUgcA3Wyn4ceUMxt+09sr/bWdzd0MiuqYitW7KUL2+RS7izw69vC Tcwiutqfx+mJoAkVpwJ5NcDBCL7YXZY3kL+Yi4tr5VviFVOvxxvnEP6s7UtwAd5cUqoD tZRw== 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 pw15si3395824ejb.583.2020.05.27.23.58.35; Wed, 27 May 2020 23:58:59 -0700 (PDT) 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 S1725939AbgE1G46 (ORCPT + 99 others); Thu, 28 May 2020 02:56:58 -0400 Received: from helcar.hmeau.com ([216.24.177.18]:34948 "EHLO fornost.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725308AbgE1G45 (ORCPT ); Thu, 28 May 2020 02:56:57 -0400 Received: from gwarestrin.arnor.me.apana.org.au ([192.168.0.7]) by fornost.hmeau.com with smtp (Exim 4.92 #5 (Debian)) id 1jeCRj-0008Jc-Vh; Thu, 28 May 2020 16:55:21 +1000 Received: by gwarestrin.arnor.me.apana.org.au (sSMTP sendmail emulation); Thu, 28 May 2020 16:55:19 +1000 Date: Thu, 28 May 2020 16:55:19 +1000 From: Herbert Xu To: "stern@rowland.harvard.edu" Cc: "Sverdlin, Alexander (Nokia - DE/Ulm)" , "dinghao.liu@zju.edu.cn" , "kjlu@umn.edu" , "mpm@selenic.com" , "gregkh@linuxfoundation.org" , "ben.dooks@codethink.co.uk" , "linux-kernel@vger.kernel.org" , "arnd@arndb.de" , "allison@lohutok.net" , "yuehaibing@huawei.com" , "rfontana@redhat.com" , "linux-crypto@vger.kernel.org" , "tglx@linutronix.de" , "Rafael J. Wysocki" Subject: Re: [PATCH] hwrng: ks-sa - fix runtime pm imbalance on error Message-ID: <20200528065519.GA26960@gondor.apana.org.au> References: <20200520132957.18776-1-dinghao.liu@zju.edu.cn> <20200520164556.GC11084@rowland.harvard.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200520164556.GC11084@rowland.harvard.edu> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Wed, May 20, 2020 at 12:45:56PM -0400, stern@rowland.harvard.edu wrote: > On Wed, May 20, 2020 at 03:42:17PM +0000, Sverdlin, Alexander (Nokia - DE/Ulm) wrote: > > Hello Dinghao, > > > > On Wed, 2020-05-20 at 21:29 +0800, Dinghao Liu wrote: > > > pm_runtime_get_sync() increments the runtime PM usage counter even > > > the call returns an error code. Thus a pairing decrement is needed > > > on the error handling path to keep the counter balanced. > > > > I believe, this is the wrong place for such kind of fix. > > pm_runtime_get_sync() has obviously a broken semantics with regards to > > your observation but no other driver does what you propose. > > Look again. For example, see what usb_autoresume_device() in > drivers/usb/core/driver.c does. However, there seems to be some disagreement as to what to do when pm_runtime_get_sync fails. Your driver chooses to call put_sync while others prefer pm_runtime_put_noidle (e.g., see drivers/base/power/runtime.c). This API does seem to be in a bit of a mess. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt