lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Sun, 31 May 2020 18:06:42 +0200
From:   Markus Elfring <>
To:     Dinghao Liu <>,
        Sylwester Nawrocki <>,,,
        Kangjie Lu <>,
        Krzysztof Kozlowski <>,
        Kukjin Kim <>,
        Kyungmin Park <>,
        Mauro Carvalho Chehab <>
Subject: Re: [PATCH] media: exynos4-is: Fix runtime PM imbalance in

> pm_runtime_get_sync() increments the runtime PM usage counter even
> when it returns an error code. Thus a pairing decrement is needed on
> the error handling path to keep the counter balanced.

How do you think about a wording variant like the following?

   Change description:
   The PM runtime usage counter is incremented even if a call of
   the function “pm_runtime_get_sync” failed. Thus decrement it also
   in an error case so that the reference counting is kept consistent.

Would you like to add the tag “Fixes” to the commit message?

Can it make sense to combine the software adjustment with the
update step “media: exynos4-is: Fix runtime PM imbalance in fimc_is_probe”?

+++ b/drivers/media/platform/exynos4-is/fimc-isp-video.c
@@ -293,6 +293,7 @@  static int isp_video_open(struct file *file)
 	if (!ret)
 		goto unlock;
+	pm_runtime_put_noidle(&isp->pdev->dev);

Is there a need to use a label like “put_pm”?


Powered by blists - more mailing lists