public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@meta.com>
To: <linux-pci@vger.kernel.org>, <helgaas@kernel.org>
Cc: <alex@shazbot.org>, <lukas@wunner.de>, <dan.j.williams@intel.com>,
	<guojinhui.liam@bytedance.com>, <ilpo.jarvinen@linux.intel.com>,
	Keith Busch <kbusch@kernel.org>
Subject: [PATCHv2 0/4] pci: slot handling fixes
Date: Fri, 30 Jan 2026 08:59:49 -0800	[thread overview]
Message-ID: <20260130165953.751063-1-kbusch@meta.com> (raw)

From: Keith Busch <kbusch@kernel.org>

This series fixes some older issues are the slot lock usage, with two
follow on patches to address multi-function resets in pcie hotplug
slots.

Previous discussions:

  https://lore.kernel.org/linux-pci/20260116184150.3013258-1-kbusch@meta.com/

  https://lore.kernel.org/linux-pci/aXvOOjZQ_EmZDgVs@kbusch-mbp/T/#t

Version change notes:

 * The first patch is unchanged from the original.

 * The second patch adds the local "bridge" to improve code clarity
   (review comments from Dan)

 * The third patch removes pci_slot_resettable in addition to all the
   other slot specific locking and state saving functions. I also
   updated a code comment explaining that all bus devices are saved and
   restored with the slot reset.

 * Included a fourth patch that fixes user suborindate bus resets when the
   bridge is pcie hotplug capable; a previous version came from this
   independent patch here:

  https://lore.kernel.org/linux-pci/20260116154244.1452246-1-kbusch@meta.com/

   And I'm including it in this series since it is all in the same area
   with slot resets. I've made a minor change to the previous version to
   remove the code duplication with pci_bus_error_reset().

Jinhui Guo (1):
  PCI: Fix incorrect unlocking in pci_slot_trylock()

Keith Busch (3):
  pci: fix slot reset device locking
  pci: remove slot specific lock/unlock and save/restore
  pci: make reset_subordinate hotplug safe

 drivers/pci/pci-sysfs.c |   3 +-
 drivers/pci/pci.c       | 213 +++++++++++-----------------------------
 drivers/pci/pci.h       |   2 +-
 3 files changed, 61 insertions(+), 157 deletions(-)

-- 
2.47.3


             reply	other threads:[~2026-01-30 17:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 16:59 Keith Busch [this message]
2026-01-30 16:59 ` [PATCHv2 1/4] PCI: Fix incorrect unlocking in pci_slot_trylock() Keith Busch
2026-01-30 16:59 ` [PATCHv2 2/4] pci: fix slot reset device locking Keith Busch
2026-01-30 16:59 ` [PATCHv2 3/4] pci: remove slot specific lock/unlock and save/restore Keith Busch
2026-01-31  5:58   ` dan.j.williams
2026-02-04 21:33     ` Keith Busch
2026-02-02 20:27   ` Keith Busch
2026-01-30 16:59 ` [PATCHv2 4/4] pci: make reset_subordinate hotplug safe Keith Busch
2026-01-31  6:42   ` dan.j.williams
2026-02-04 22:31     ` Keith Busch
2026-01-31  0:18 ` [PATCHv2 0/4] pci: slot handling fixes Bjorn Helgaas

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=20260130165953.751063-1-kbusch@meta.com \
    --to=kbusch@meta.com \
    --cc=alex@shazbot.org \
    --cc=dan.j.williams@intel.com \
    --cc=guojinhui.liam@bytedance.com \
    --cc=helgaas@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --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