From: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Navid Emamdoost
<navid.emamdoost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Laxman Dewangan
<ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: emamd001-OJFnDUYgAso@public.gmane.org,
wu000273-OJFnDUYgAso@public.gmane.org,
kjlu-OJFnDUYgAso@public.gmane.org,
mccamant-k0Ej6N9cQa43uPMLIKxrzw@public.gmane.org
Subject: Re: [PATCH] spi: tegra114: missing put on pm_runtime_get_sync failure
Date: Fri, 5 Jun 2020 07:09:03 +0100 [thread overview]
Message-ID: <f928fb02-47d7-b6f9-6198-bd549d6ac6b5@nvidia.com> (raw)
In-Reply-To: <20200602045506.40574-1-navid.emamdoost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 02/06/2020 05:55, Navid Emamdoost wrote:
> the call to pm_runtime_get_sync increments the counter even
> in case of failure leading to incorrect ref count.
> Call pm_runtime_put if pm_runtime_get_sync fails.
>
> Signed-off-by: Navid Emamdoost <navid.emamdoost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> drivers/spi/spi-tegra114.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/spi/spi-tegra114.c b/drivers/spi/spi-tegra114.c
> index 83edabdb41ad..dccd2ac1a975 100644
> --- a/drivers/spi/spi-tegra114.c
> +++ b/drivers/spi/spi-tegra114.c
> @@ -974,6 +974,7 @@ static int tegra_spi_setup(struct spi_device *spi)
> dev_err(tspi->dev, "pm runtime failed, e = %d\n", ret);
> if (cdata)
> tegra_spi_cleanup(spi);
> + pm_runtime_put(tspi->dev);
> return ret;
> }
>
> @@ -1398,6 +1399,7 @@ static int tegra_spi_probe(struct platform_device *pdev)
> ret = pm_runtime_get_sync(&pdev->dev);
> if (ret < 0) {
> dev_err(&pdev->dev, "pm runtime get failed, e = %d\n", ret);
> + pm_runtime_put(&pdev->dev);
> goto exit_pm_disable;
> }
I am wondering if it is better we use put_sync() here to ensure that
this happens before we exit the probe.
Jon
--
nvpublic
next prev parent reply other threads:[~2020-06-05 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 4:55 [PATCH] spi: tegra114: missing put on pm_runtime_get_sync failure Navid Emamdoost
[not found] ` <20200602045506.40574-1-navid.emamdoost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-06-05 6:09 ` Jon Hunter [this message]
[not found] ` <f928fb02-47d7-b6f9-6198-bd549d6ac6b5-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2020-06-05 6:13 ` Navid Emamdoost
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=f928fb02-47d7-b6f9-6198-bd549d6ac6b5@nvidia.com \
--to=jonathanh-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=emamd001-OJFnDUYgAso@public.gmane.org \
--cc=kjlu-OJFnDUYgAso@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mccamant-k0Ej6N9cQa43uPMLIKxrzw@public.gmane.org \
--cc=navid.emamdoost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=wu000273-OJFnDUYgAso@public.gmane.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