Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp1191121pxu; Fri, 27 Nov 2020 01:44:51 -0800 (PST) X-Google-Smtp-Source: ABdhPJzq6NltrCztNzqtq2GLRnI4BEIJf0sf1miw+DYLlx2EqPdgy0cPBUsZcbpXQqJlLmxrSZNR X-Received: by 2002:a17:906:fa8b:: with SMTP id lt11mr2091815ejb.94.1606470291393; Fri, 27 Nov 2020 01:44:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606470291; cv=none; d=google.com; s=arc-20160816; b=af3S/Q/qlaIoQii0eSGdcyUWsGAitTWPB3Ki1aYedWmW0nYwkVrwJ/wwBiPWx+NMym HfW3oCrcIvpN7SFTQixVwTOKuiDM5QQZg1A2Uw+XmIHUVHAOFaIctTTZ/biGyh+ldIfW s1ZxdA8ME1dLpMpePmoOXtOGA/6TJi40Sjjk97U/2xB8emhE35wE9iUkSBkNo4Cvkapk iDzQWY5mmxnU4WWfbGnAQsAj+Kkmev2ZeRuKhzp1MSA62EtEV5K8hj8yanqo7IIdvGvO rlVVVlPtrRCGbhFHsE8T59rk0tH3nNC+Ug5z/sEaxaBL748TfVi+VL+JYCRukIjL9JUo 6prg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=0rcaXN0DZqE7YXIm9z0wb34aVoGoLqt6Pi2bXEDuuYM=; b=p6ILI41uCff5/QxhQ+HEgZHPKsLSs6GkpBcSXSu1ElUCGOt/rSIipz1SMYq7bUU28X S+YHkEQQxDT1HYNGvs1TdYeCCWwXz1o33Nf/nrBYdpd8ojxQ9rJKx6R+CtOSQadpxMDU dNXo259rNUf7CtUs594H/+u8s4IgPJjy7YKhhO4Ckf6l319dfTZShQATHYBAFqU+i9WT QtoKWzFzqS+qL760uGhyrwgIuN+mp4sElZkyeD6ckKAORdQ9RjzYqnl5cpgb6Kr4GlIX u9HgjTAWDNWfLpngflqSZMm/Tmgwn+2BTUlUfh1y19Tzu2BQY0s0/RfLlqol0B7NTGOL GC5A== 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d20si4729392ejb.512.2020.11.27.01.44.28; Fri, 27 Nov 2020 01:44:51 -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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726952AbgK0JoU (ORCPT + 99 others); Fri, 27 Nov 2020 04:44:20 -0500 Received: from mail-wm1-f68.google.com ([209.85.128.68]:33542 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725989AbgK0JoT (ORCPT ); Fri, 27 Nov 2020 04:44:19 -0500 Received: by mail-wm1-f68.google.com with SMTP id u10so1331195wmm.0; Fri, 27 Nov 2020 01:44:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=0rcaXN0DZqE7YXIm9z0wb34aVoGoLqt6Pi2bXEDuuYM=; b=dB3RawjokfsPRLTP29G3EU4Ngjw3pnL3yXZTnbUCiR0hDNQoqMo9yJh9aTmy2w+VZv 1dsfx4dMf3R4ybMsrbsS7y4p+y5v8BcxkPpiJ/0yJKO+609kM052YrOE25EpFIZ0n5qo XEXF60HrZ7v0kAKNC+B5zN+N0WiJjU8VTci3wYPzPp549a+n41tA6zHEFFTc+s5ip8ck PI3ZkPft0SFUqGcgTPLaIazMPD56WM4FQV4HXOLJEuGiZO9AD8YjkKEOCw7u59CCOMiu UV/oiGmcKOIejXjdaIVowqEsYxvlf6kUm5PRqtvk1kylz7ZqbVUqBySE+5QbiM4h35Sb GB7g== X-Gm-Message-State: AOAM53021ZbUd51uwsWo4w2PNMGp5J3wfJn4pYV63zeguMev3+tI5XUK amqukWSpIvGrl6/nz/8CfG8= X-Received: by 2002:a1c:9dd7:: with SMTP id g206mr8199701wme.49.1606470256949; Fri, 27 Nov 2020 01:44:16 -0800 (PST) Received: from kozik-lap (adsl-84-226-167-205.adslplus.ch. [84.226.167.205]) by smtp.googlemail.com with ESMTPSA id o13sm12131106wmc.44.2020.11.27.01.44.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 27 Nov 2020 01:44:15 -0800 (PST) Date: Fri, 27 Nov 2020 10:44:14 +0100 From: Krzysztof Kozlowski To: Qinglang Miao Cc: =?utf-8?Q?=C5=81ukasz?= Stelmach , linux-samsung-soc@vger.kernel.org, linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] hwrng: exynos - fix reference leak in exynos_trng_probe Message-ID: <20201127094414.GA10679@kozik-lap> References: <20201127094446.121277-1-miaoqinglang@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20201127094446.121277-1-miaoqinglang@huawei.com> Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Fri, Nov 27, 2020 at 05:44:46PM +0800, Qinglang Miao wrote: > pm_runtime_get_sync will increment pm usage counter even it > failed. Forgetting to putting operation will result in a > reference leak here. > > A new function pm_runtime_resume_and_get is introduced in > [0] to keep usage counter balanced. So We fix the reference > leak by replacing it with new funtion. > > [0] dd8088d5a896 ("PM: runtime: Add pm_runtime_resume_and_get to deal with usage counter") Do not put such dependencies into the commit message - it does not bring useful information to the history. Store it under '---' separator. > > Fixes: 6cd225cc5d8a ("hwrng: exynos - add Samsung Exynos True RNG driver") > Reported-by: Hulk Robot > Signed-off-by: Qinglang Miao > --- > drivers/char/hw_random/exynos-trng.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/char/hw_random/exynos-trng.c b/drivers/char/hw_random/exynos-trng.c > index 8e1fe3f8d..666246bc8 100644 > --- a/drivers/char/hw_random/exynos-trng.c > +++ b/drivers/char/hw_random/exynos-trng.c > @@ -132,7 +132,7 @@ static int exynos_trng_probe(struct platform_device *pdev) > return PTR_ERR(trng->mem); > > pm_runtime_enable(&pdev->dev); > - ret = pm_runtime_get_sync(&pdev->dev); > + ret = pm_runtime_resume_and_get(&pdev->dev); This cannot be applied. Fix it by replacing err_clock label with this one. Best regards, Krzysztof