From: Jiabing Wan <wanjiabing@vivo.com>
To: Rob Herring <robh@kernel.org>, Bjorn Helgaas <helgaas@kernel.org>
Cc: "Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
"Xiaowei Song" <songxiaowei@hisilicon.com>,
"Binghui Wang" <wangbinghui@hisilicon.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
PCI <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jiabing.wan@qq.com
Subject: Re: [PATCH] PCI: kirin: Fix of_node_put() issue in pcie-kirin
Date: Fri, 5 Nov 2021 09:52:44 +0800 [thread overview]
Message-ID: <8819ab07-9cbf-dc68-34c8-69d67cae53c5@vivo.com> (raw)
In-Reply-To: <AF*AtQCaEjn8dlEJIiS9Xqqm.9.1636034225636.Hmail.wanjiabing@vivo.com>
On 2021/11/4 21:56, Rob Herring wrote:
> On Wed, Nov 3, 2021 at 9:31 AM Bjorn Helgaas <helgaas@kernel.org> wrote:
>> [+to Mauro, author of code being changed,
>> Rob for "of_pci_get_devfn()" naming question]
>>
>> On Wed, Nov 03, 2021 at 02:25:18AM -0400, Wan Jiabing wrote:
>>> Fix following coccicheck warning:
>>> ./drivers/pci/controller/dwc/pcie-kirin.c:414:2-34: WARNING: Function
>>> for_each_available_child_of_node should have of_node_put() before return.
>>>
>>> Early exits from for_each_available_child_of_node should decrement the
>>> node reference counter. Replace return by goto here.
>>>
>>> Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
>>> ---
>>> drivers/pci/controller/dwc/pcie-kirin.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/pci/controller/dwc/pcie-kirin.c b/drivers/pci/controller/dwc/pcie-kirin.c
>>> index 06017e826832..23a2c076ce53 100644
>>> --- a/drivers/pci/controller/dwc/pcie-kirin.c
>>> +++ b/drivers/pci/controller/dwc/pcie-kirin.c
>>> @@ -422,7 +422,8 @@ static int kirin_pcie_parse_port(struct kirin_pcie *pcie,
>>> pcie->num_slots++;
>>> if (pcie->num_slots > MAX_PCI_SLOTS) {
>>> dev_err(dev, "Too many PCI slots!\n");
>>> - return -EINVAL;
>>> + ret = -EINVAL;
>>> + goto put_node;
>>> }
>>>
>>> ret = of_pci_get_devfn(child);
>> This is a change to the code added here:
>> https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?id=31bd24f0cfe0
>>
>> This fix looks right to me; all the other early exits from the inner
>> loop drop the "child" reference.
>>
>> But this is a nested loop and the *outer* loop also increments
>> refcounts, and I don't see that outer loop reference on "parent" being
>> dropped at all:
>>
>> for_each_available_child_of_node(node, parent) {
>> for_each_available_child_of_node(parent, child) {
>> ...
>> if (error)
>> goto put_node;
>> }
>> }
>>
>> put_node:
>> of_node_put(child);
> Indeed. There should be a put on the parent.
OK, I'll fix in v2. Thanks.
Jiabing Wan
prev parent reply other threads:[~2021-11-05 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 6:25 Wan Jiabing
2021-11-03 14:30 ` Bjorn Helgaas
2021-11-04 13:56 ` Rob Herring
[not found] ` <AF*AtQCaEjn8dlEJIiS9Xqqm.9.1636034225636.Hmail.wanjiabing@vivo.com>
2021-11-05 1:52 ` Jiabing Wan [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=8819ab07-9cbf-dc68-34c8-69d67cae53c5@vivo.com \
--to=wanjiabing@vivo.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jiabing.wan@qq.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mchehab+huawei@kernel.org \
--cc=robh@kernel.org \
--cc=songxiaowei@hisilicon.com \
--cc=wangbinghui@hisilicon.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®