From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Johan Hovold <johan@kernel.org>
Cc: Murali Karicheri <m-karicheri2@ti.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] PCI: keystone: fix interrupt-controller-node lookup
Date: Fri, 17 Nov 2017 11:19:10 +0000 [thread overview]
Message-ID: <20171117111910.GA21148@red-moon> (raw)
In-Reply-To: <20171112122850.30804-1-johan@kernel.org>
Hi Johan,
On Sun, Nov 12, 2017 at 01:28:50PM +0100, Johan Hovold wrote:
> Fix child-node lookup during initialisation, which ended up searching
> the whole device tree depth-first starting at the parent rather than
> just matching on its children.
>
> To make things worse, the parent pci node was prematurely freed, while
> the child interrupt-controller node was leaked.
I think you should explain that of_find_node_by_name() drops a reference
to the from pointer, it is not clear from the log.
More importantly: are you saying that all of_find_node_by_name() usages
with a (from* != NULL) are broken unless they bump up the from node (if
!= NULL) ref count ?
Is there a reason why of_find_node_by_name() behaviour can't be changed ?
> Fixes: 0c4ffcfe1fbc ("PCI: keystone: Add TI Keystone PCIe driver")
> Cc: stable <stable@vger.kernel.org> # 3.18
Do we really want to send this to stable kernels straight away ?
There is not any specific bug report - it should be safe but I
wanted to ask.
> Cc: Murali Karicheri <m-karicheri2@ti.com>
> ---
> drivers/pci/dwc/pci-keystone.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
With an update log:
Acked-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> diff --git a/drivers/pci/dwc/pci-keystone.c b/drivers/pci/dwc/pci-keystone.c
> index 5bee3af47588..39405598b22d 100644
> --- a/drivers/pci/dwc/pci-keystone.c
> +++ b/drivers/pci/dwc/pci-keystone.c
> @@ -178,7 +178,7 @@ static int ks_pcie_get_irq_controller_info(struct keystone_pcie *ks_pcie,
> }
>
> /* interrupt controller is in a child node */
> - *np_temp = of_find_node_by_name(np_pcie, controller);
> + *np_temp = of_get_child_by_name(np_pcie, controller);
> if (!(*np_temp)) {
> dev_err(dev, "Node for %s is absent\n", controller);
> return -EINVAL;
> @@ -187,6 +187,7 @@ static int ks_pcie_get_irq_controller_info(struct keystone_pcie *ks_pcie,
> temp = of_irq_count(*np_temp);
> if (!temp) {
> dev_err(dev, "No IRQ entries in %s\n", controller);
> + of_node_put(*np_temp);
> return -EINVAL;
> }
>
> @@ -204,6 +205,8 @@ static int ks_pcie_get_irq_controller_info(struct keystone_pcie *ks_pcie,
> break;
> }
>
> + of_node_put(*np_temp);
> +
> if (temp) {
> *num_irqs = temp;
> return 0;
> --
> 2.15.0
>
next prev parent reply other threads:[~2017-11-17 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 12:28 [PATCH] PCI: keystone: fix interrupt-controller-node lookup Johan Hovold
2017-11-13 10:43 ` Lorenzo Pieralisi
2017-11-13 17:26 ` Karicheri, Muralidharan
2017-11-14 17:34 ` Johan Hovold
2017-11-15 18:15 ` Lorenzo Pieralisi
2017-11-17 11:19 ` Lorenzo Pieralisi [this message]
2017-11-17 12:59 ` Johan Hovold
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=20171117111910.GA21148@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).