linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: Pratyush Yadav <p.yadav@ti.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: i2c: ov5648: Plug runtime pm counter leak
Date: Fri, 21 May 2021 17:00:38 +0300	[thread overview]
Message-ID: <20210521140037.GA3@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <20210511124437.9930-1-p.yadav@ti.com>

Hi Pratyush,

Thanks for the patch.

On Tue, May 11, 2021 at 06:14:37PM +0530, Pratyush Yadav wrote:
> When the stream is being enabled, the runtime pm usage counter is
> incremented. Then if ov5648_sw_standby() fails, the function returns
> error without decrementing the counter, leaking it.
> 
> Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
> ---
> 
> Hi,
> 
> I spotted this when converting OV5640 driver to use runtime PM using
> this driver as reference. I only have a very surface level understanding
> of runtime PM system as of now so please review with that in mind.
> 
> This patch is only compile-tested since I don't have the hardware with
> me.
> 
>  drivers/media/i2c/ov5648.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/media/i2c/ov5648.c b/drivers/media/i2c/ov5648.c
> index 3ecb4a3e8773..6aa2c950f505 100644
> --- a/drivers/media/i2c/ov5648.c
> +++ b/drivers/media/i2c/ov5648.c
> @@ -2143,8 +2143,12 @@ static int ov5648_s_stream(struct v4l2_subdev *subdev, int enable)
>  	ret = ov5648_sw_standby(sensor, !enable);
>  	mutex_unlock(&sensor->mutex);
> 
> -	if (ret)
> +	if (ret) {
> +		if (enable)
> +			pm_runtime_put(sensor->dev);

The function powers the sensor off at the end if streaming was to be
disabled. You could do:

	if (ret || !enable)
		pm_runtime_put(sensor->dev);

> +
>  		return ret;
> +	}
> 
>  	state->streaming = !!enable;

state->streaming is assigned when not holding the lock. Could you address
that at the same time?

-- 
Kind regards,

Sakari Ailus

      reply	other threads:[~2021-05-21 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 12:44 [PATCH] media: i2c: ov5648: Plug runtime pm counter leak Pratyush Yadav
2021-05-21 14:00 ` Sakari Ailus [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=20210521140037.GA3@valkosipuli.retiisi.eu \
    --to=sakari.ailus@iki.fi \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=p.yadav@ti.com \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=sakari.ailus@linux.intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).