From: kernel test robot <lkp@intel.com>
To: Keith Busch <kbusch@meta.com>,
linux-pci@vger.kernel.org, lukas@wunner.de, bhelgaas@google.com
Cc: oe-kbuild-all@lists.linux.dev, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH 1/2] PCI: pciehp: fix concurrent sub-tree removal deadlock
Date: Tue, 11 Jun 2024 14:19:09 +0800 [thread overview]
Message-ID: <202406111416.XIxUrEy4-lkp@intel.com> (raw)
In-Reply-To: <20240610220304.3162895-2-kbusch@meta.com>
Hi Keith,
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 v6.10-rc3 next-20240607]
[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/Keith-Busch/PCI-pciehp-fix-concurrent-sub-tree-removal-deadlock/20240611-060555
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20240610220304.3162895-2-kbusch%40meta.com
patch subject: [PATCH 1/2] PCI: pciehp: fix concurrent sub-tree removal deadlock
config: arc-allnoconfig (https://download.01.org/0day-ci/archive/20240611/202406111416.XIxUrEy4-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240611/202406111416.XIxUrEy4-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/202406111416.XIxUrEy4-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/pci/of.c:16:
drivers/pci/pci.h: In function 'pci_dev_set_disconnected':
>> drivers/pci/pci.h:416:9: error: implicit declaration of function 'pci_notify_disconnected'; did you mean 'pci_doe_disconnected'? [-Werror=implicit-function-declaration]
416 | pci_notify_disconnected();
| ^~~~~~~~~~~~~~~~~~~~~~~
| pci_doe_disconnected
cc1: some warnings being treated as errors
vim +416 drivers/pci/pci.h
411
412 static inline int pci_dev_set_disconnected(struct pci_dev *dev, void *unused)
413 {
414 pci_dev_set_io_state(dev, pci_channel_io_perm_failure);
415 pci_doe_disconnected(dev);
> 416 pci_notify_disconnected();
417
418 return 0;
419 }
420
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-06-11 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 22:03 [PATCH 0/2] pcie hotplug and error fixes Keith Busch
2024-06-10 22:03 ` [PATCH 1/2] PCI: pciehp: fix concurrent sub-tree removal deadlock Keith Busch
2024-06-11 6:19 ` kernel test robot
2024-06-11 6:19 ` kernel test robot [this message]
2024-06-11 14:33 ` Keith Busch
2024-06-10 22:03 ` [PATCH 2/2] PCI: err: ensure stable topology during handling Keith Busch
-- strict thread matches above, loose matches on Subject: below --
2024-06-12 18:10 [PATCH 0/2] pcie hotplug and error fixes Keith Busch
2024-06-12 18:10 ` [PATCH 1/2] PCI: pciehp: fix concurrent sub-tree removal deadlock Keith Busch
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=202406111416.XIxUrEy4-lkp@intel.com \
--to=lkp@intel.com \
--cc=bhelgaas@google.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=oe-kbuild-all@lists.linux.dev \
/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