linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: zhangqilong <zhangqilong3@huawei.com>, vidyas@nvidia.com
Cc: "robh@kernel.org" <robh@kernel.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: 答复: [PATCH] PCI: dwc: fix reference leak in pex_ep_event_pex_rst_deassert
Date: Mon, 25 Jan 2021 16:34:31 +0000	[thread overview]
Message-ID: <20210125163431.GB5795@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <b1f6b6805a7746b48020d7cfaaa73fab@huawei.com>

On Tue, Nov 03, 2020 at 03:14:21AM +0000, zhangqilong wrote:
> Hi
> 
> > 
> > 
> > On 11/2/2020 8:00 PM, Zhang Qilong wrote:
> > > External email: Use caution opening links or attachments
> > >
> > >
> > > pm_runtime_get_sync will increment pm usage counter even it failed.
> > > Forgetting to pm_runtime_put_noidle will result in reference leak in
> > > pex_ep_event_pex_rst_deassert, so we should fix it.
> > >
> > > Fixes: c57247f940e8e ("PCI: tegra: Add support for PCIe endpoint mode
> > > in Tegra194")
> > > Signed-off-by: Zhang Qilong <zhangqilong3@huawei.com>
> > > ---
> > >   drivers/pci/controller/dwc/pcie-tegra194.c | 1 +
> > >   1 file changed, 1 insertion(+)
> > >
> > > diff --git a/drivers/pci/controller/dwc/pcie-tegra194.c
> > > b/drivers/pci/controller/dwc/pcie-tegra194.c
> > > index f920e7efe118..936510b5c649 100644
> > > --- a/drivers/pci/controller/dwc/pcie-tegra194.c
> > > +++ b/drivers/pci/controller/dwc/pcie-tegra194.c
> > > @@ -1662,6 +1662,7 @@ static void pex_ep_event_pex_rst_deassert(struct
> > > tegra_pcie_dw *pcie)
> > >
> > >          ret = pm_runtime_get_sync(dev);
> > >          if (ret < 0) {
> > > +               pm_runtime_put_noidle(dev);
> > Why can't we call pm_runtime_put_sync(dev) as that is what is being called in
> > failure cases anyway further down in this API?
> > 
> Both of the two functions are OK, the difference is that, when pm_runtime_put_sync failed(runtime of the device has error, the device is in Inaccessible state or other error state...), it only increase the usage count of the power, and do nothing else. We merely need call pm_runtime_put_noidle to decrease the usage count. If we call pm_runtime_put_sync to reset it, it will notify device bus type if the device can be suspended, and that is meanless when pm_runtime_put_sync failed.

I don't understand. Vidya any feedback ?

Lorenzo

> Thanks, best wish!
> 
> Zhang Qilong
> > >                  dev_err(dev, "Failed to get runtime sync for PCIe
> > dev: %d\n",
> > >                          ret);
> > >                  return;
> > > --
> > > 2.17.1
> > >

  reply	other threads:[~2021-01-25 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 14:30 [PATCH] PCI: dwc: fix reference leak in pex_ep_event_pex_rst_deassert Zhang Qilong
2020-11-03  2:52 ` Vidya Sagar
2020-11-03  3:14   ` 答复: " zhangqilong
2021-01-25 16:34     ` Lorenzo Pieralisi [this message]
2021-01-27  6:19       ` Vidya Sagar
2021-01-25 19:30   ` Jon Hunter
2021-03-23 10:24     ` Lorenzo Pieralisi

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=20210125163431.GB5795@e121166-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=bhelgaas@google.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=vidyas@nvidia.com \
    --cc=zhangqilong3@huawei.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).