From: Qinglang Miao <miaoqinglang@huawei.com>
To: Lukasz Stelmach <l.stelmach@samsung.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
<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
Date: Mon, 30 Nov 2020 21:05:55 +0800 [thread overview]
Message-ID: <3ed654dd-db10-0975-d125-a3949c9bab90@huawei.com> (raw)
In-Reply-To: <dleftjlfemg9kh.fsf%l.stelmach@samsung.com>
在 2020/11/27 22:26, Lukasz Stelmach 写道:
> It was <2020-11-27 pią 17:44>, when 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")
>>
>> Fixes: 6cd225cc5d8a ("hwrng: exynos - add Samsung Exynos True RNG driver")
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Signed-off-by: Qinglang Miao <miaoqinglang@huawei.com>
>> ---
>> 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);
>> if (ret < 0) {
>> dev_err(&pdev->dev, "Could not get runtime PM.\n");
>> goto err_pm_get;
>
> Thanks. I suppose you may use the new function exynos_trng_resume(),
> remove everything and leave only
>
> return pm_runtime_resume_and_get(dev);
Hi, Lukasz
I sent a v2 on this one.
But I'm not really sure about what does 'remove everything' mean. for
example, should I remove exynos_trng_resume in this patch?
Thanks.
>
prev parent reply other threads:[~2020-11-30 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201127142637eucas1p1746be156c43e789b48b5b78b9b212a33@eucas1p1.samsung.com>
2020-11-27 9:44 ` [PATCH] hwrng: exynos - fix reference leak in exynos_trng_probe Qinglang Miao
2020-11-27 9:44 ` Krzysztof Kozlowski
2020-11-30 13:03 ` Qinglang Miao
2020-11-27 14:26 ` Lukasz Stelmach
2020-11-30 13:05 ` Qinglang Miao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ed654dd-db10-0975-d125-a3949c9bab90@huawei.com \
--to=miaoqinglang@huawei.com \
--cc=krzk@kernel.org \
--cc=l.stelmach@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox