From: kernel test robot <lkp@intel.com>
To: Wentao Liang <vulab@iscas.ac.cn>, Liviu.Dudau@arm.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
bhelgaas@google.com, kwilczynski@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
lpieralisi@kernel.org, mani@kernel.org, robh@kernel.org,
tinamdar@apm.com, toan@os.amperecomputing.com,
Wentao Liang <vulab@iscas.ac.cn>,
stable@vger.kernel.org
Subject: Re: [PATCH] PCI: xgene: Fix device node reference leak in xgene_pcie_probe()
Date: Fri, 18 Sep 2026 19:50:23 +0800 [thread overview]
Message-ID: <202609181924.6ZUpd4Ww-lkp@intel.com> (raw)
In-Reply-To: <20260917132235.2153154-1-vulab@iscas.ac.cn>
Hi Wentao,
kernel test robot noticed the following build errors:
[auto build test ERROR on pci/next]
[also build test ERROR on pci/for-linus linus/master v7.3-rc3 next-20260916]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Wentao-Liang/PCI-xgene-Fix-device-node-reference-leak-in-xgene_pcie_probe/20260917-132235
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20260917132235.2153154-1-vulab%40iscas.ac.cn
patch subject: [PATCH] PCI: xgene: Fix device node reference leak in xgene_pcie_probe()
config: riscv-randconfig-1001-20260918 (https://download.01.org/0day-ci/archive/20260918/202609181924.6ZUpd4Ww-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 7252edd9aa82ef1c570ff6694ef7f4763a8a5d2f)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260918/202609181924.6ZUpd4Ww-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609181924.6ZUpd4Ww-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/pci/controller/pci-xgene.c:646:20: error: no member named 'node' in 'struct xgene_pcie'
646 | of_node_put(port->node);
| ~~~~ ^
1 error generated.
vim +646 drivers/pci/controller/pci-xgene.c
603
604 static int xgene_pcie_probe(struct platform_device *pdev)
605 {
606 struct device *dev = &pdev->dev;
607 struct xgene_pcie *port;
608 struct pci_host_bridge *bridge;
609 int ret;
610
611 if (!xgene_check_pcie_msi_ready())
612 return dev_err_probe(&pdev->dev, -EPROBE_DEFER,
613 "MSI driver not ready\n");
614
615 bridge = devm_pci_alloc_host_bridge(dev, sizeof(*port));
616 if (!bridge)
617 return -ENOMEM;
618
619 port = pci_host_bridge_priv(bridge);
620
621 port->dev = dev;
622 port->version = XGENE_PCIE_IP_VER_1;
623
624 ret = xgene_pcie_map_reg(port, pdev);
625 if (ret)
626 goto err_put_node;
627
628 ret = xgene_pcie_init_port(port);
629 if (ret)
630 goto err_put_node;
631
632 ret = xgene_pcie_setup(port);
633 if (ret)
634 goto err_put_node;
635
636 bridge->sysdata = port;
637 bridge->ops = &xgene_pcie_ops;
638
639 ret = pci_host_probe(bridge);
640 if (ret)
641 goto err_put_node;
642
643 return 0;
644
645 err_put_node:
> 646 of_node_put(port->node);
647 return ret;
648 }
649
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-09-18 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 13:22 Wentao Liang
2026-09-18 11:50 ` kernel test robot [this message]
2026-09-18 12:37 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2026-08-14 13:41 Ruoyu Wang
2026-09-10 12:23 ` 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=202609181924.6ZUpd4Ww-lkp@intel.com \
--to=lkp@intel.com \
--cc=Liviu.Dudau@arm.com \
--cc=bhelgaas@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tinamdar@apm.com \
--cc=toan@os.amperecomputing.com \
--cc=vulab@iscas.ac.cn \
/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®