Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@meta.com>
To: <linux-pci@vger.kernel.org>, <lukas@wunner.de>, <helgaas@kernel.org>
Cc: Keith Busch <kbusch@kernel.org>
Subject: [PATCH RESEND 0/1] pcie hotplug deadlock fix
Date: Thu, 16 Oct 2025 12:30:48 -0700	[thread overview]
Message-ID: <20251016193049.881212-1-kbusch@meta.com> (raw)

From: Keith Busch <kbusch@kernel.org>

It's been a while since the last resend, and no movement on this so far.
This problem has been reported multiple times over the years, first one
I can find is from here:

  https://lore.kernel.org/lkml/1519648875-38196-1-git-send-email-wangxiongfeng2@huawei.com/

Lacking any other progress, I once again ask that we can take fixes for
this issue, as perfection is the providing to be a blocker to
improvement. The patch from this series is what we run in the Meta fleet
already and it has proven tremendously valuable at maintaining uptime
across the machines. No issues have been found with running it, so
asking once again if we can consider it for upstream.

Keith Busch (1):
  PCI: pciehp: fix concurrent sub-tree removal deadlock

 drivers/pci/hotplug/pciehp_pci.c | 12 +++++++++---
 drivers/pci/pci.h                |  1 +
 drivers/pci/probe.c              | 25 +++++++++++++++++++++++++
 include/linux/pci.h              |  2 ++
 4 files changed, 37 insertions(+), 3 deletions(-)

-- 
2.47.3


             reply	other threads:[~2025-10-16 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 19:30 Keith Busch [this message]
2025-10-16 19:30 ` [PATCH RESEND 1/1] PCI: pciehp: fix concurrent sub-tree removal deadlock Keith Busch
2025-10-17 10:06   ` kernel test robot
2025-10-17 10:06   ` kernel test robot

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=20251016193049.881212-1-kbusch@meta.com \
    --to=kbusch@meta.com \
    --cc=helgaas@kernel.org \
    --cc=kbusch@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    /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