From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <kbusch@meta.com>
Cc: linux-pci@vger.kernel.org, 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: Re: [PATCHv2 0/4] pci: slot handling fixes
Date: Fri, 30 Jan 2026 18:18:53 -0600 [thread overview]
Message-ID: <20260131001853.GA31112@bhelgaas> (raw)
In-Reply-To: <20260130165953.751063-1-kbusch@meta.com>
On Fri, Jan 30, 2026 at 08:59:49AM -0800, Keith Busch wrote:
> 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(-)
Applied the first two on pci/virtualization for now (the first was
already there):
67bcd817a012 ("PCI: Fix pci_slot_trylock() error handling")
c6a26e539649 ("PCI: Fix pci_slot_lock () device locking")
If we get a review for the others I'll add them on top.
Thanks!
prev parent reply other threads:[~2026-01-31 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 16:59 [PATCHv2 0/4] pci: slot handling fixes Keith Busch
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 ` Bjorn Helgaas [this message]
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=20260131001853.GA31112@bhelgaas \
--to=helgaas@kernel.org \
--cc=alex@shazbot.org \
--cc=dan.j.williams@intel.com \
--cc=guojinhui.liam@bytedance.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--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