mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans Zhang <18255117159@163.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
	bhelgaas@google.com, s-vadapalli@ti.com,
	thomas.richard@bootlin.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, rockswang7@gmail.com
Subject: Re: [PATCH v2] PCI: cadence: Fix runtime atomic count underflow.
Date: Sun, 20 Apr 2025 09:24:35 +0800	[thread overview]
Message-ID: <348fd943-3ada-4688-bafc-3b6095e86b61@163.com> (raw)
In-Reply-To: <pjacxodfaywqxabqeftguqcrz2eoib5l5l32oevy5j5rrwl5s6@hhglbkyrmnzg>



On 2025/4/20 00:51, Manivannan Sadhasivam wrote:
> On Sat, Apr 19, 2025 at 09:30:58PM +0800, Hans Zhang wrote:
>> If the call to pci_host_probe() in cdns_pcie_host_setup()
>> fails, PM runtime count is decremented in the error path using
>> pm_runtime_put_sync().But the runtime count is not incremented by this
>> driver, but only by the callers (cdns_plat_pcie_probe/j721e_pcie_probe).
>> And the callers also decrement theruntime PM count in their error path.
>> So this leads to the below warning from the PM core:
>>
>> runtime PM usage count underflow!
>>
>> So fix it by getting rid of pm_runtime_put_sync() in the error path and
>> directly return the errno.
>>
>> Fixes: 1b79c5284439 ("PCI: cadence: Add host driver for Cadence PCIe controller")
>>
> 
> This is not the correct Fixes commit. In fact it took me a while to find the
> correct one. This exact same issue was already fixed by commit, 19abcd790b51
> ("PCI: cadence: Fix cdns_pcie_{host|ep}_setup() error path").
> 
> But then, this bug got reintroduced while fixing the merge conflict in:
> 49e427e6bdd1 ("Merge branch 'pci/host-probe-refactor'")
> 
> I will change the tag while applying.
> 

Hi Mani,

Thank you very much.

Best regards,
Hans

> - Mani
> 
>> Signed-off-by: Hans Zhang <18255117159@163.com>
>> ---
>>   drivers/pci/controller/cadence/pcie-cadence-host.c | 11 +----------
>>   1 file changed, 1 insertion(+), 10 deletions(-)
>>
>> diff --git a/drivers/pci/controller/cadence/pcie-cadence-host.c b/drivers/pci/controller/cadence/pcie-cadence-host.c
>> index 8af95e9da7ce..741e10a575ec 100644
>> --- a/drivers/pci/controller/cadence/pcie-cadence-host.c
>> +++ b/drivers/pci/controller/cadence/pcie-cadence-host.c
>> @@ -570,14 +570,5 @@ int cdns_pcie_host_setup(struct cdns_pcie_rc *rc)
>>   	if (!bridge->ops)
>>   		bridge->ops = &cdns_pcie_host_ops;
>>   
>> -	ret = pci_host_probe(bridge);
>> -	if (ret < 0)
>> -		goto err_init;
>> -
>> -	return 0;
>> -
>> - err_init:
>> -	pm_runtime_put_sync(dev);
>> -
>> -	return ret;
>> +	return pci_host_probe(bridge);
>>   }
>>
>> base-commit: a24588245776dafc227243a01bfbeb8a59bafba9
>> -- 
>> 2.25.1
>>
> 


  reply	other threads:[~2025-04-20  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-19 13:30 Hans Zhang
2025-04-19 16:51 ` Manivannan Sadhasivam
2025-04-20  1:24   ` Hans Zhang [this message]
2025-04-19 16:54 ` Manivannan Sadhasivam

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=348fd943-3ada-4688-bafc-3b6095e86b61@163.com \
    --to=18255117159@163.com \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh@kernel.org \
    --cc=rockswang7@gmail.com \
    --cc=s-vadapalli@ti.com \
    --cc=thomas.richard@bootlin.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

all inboxes | Powered by JetHome®