From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Keith Busch <kbusch@meta.com>
Cc: linux-pci@vger.kernel.org, helgaas@kernel.org, alex@shazbot.org,
dan.j.williams@intel.com, Lukas Wunner <lukas@wunner.de>,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv4 3/3] pci: make reset_subordinate hotplug safe
Date: Fri, 13 Feb 2026 09:32:32 +0200 (EET) [thread overview]
Message-ID: <04516225-9967-fd1e-c756-6963719aa08d@linux.intel.com> (raw)
In-Reply-To: <20260212224112.1913980-4-kbusch@meta.com>
On Thu, 12 Feb 2026, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> Use the slot reset method when resetting the bridge if the bus contains
> hot plug slots. This fixes spurious hot plug events that are triggered
> by the secondary bus reset that bypasses the slot's detection disabling.
>
> Resetting a bridge's subordinate bus can be done like this:
>
> # echo 1 > /sys/bus/pci/devices/0000:50:01.0/reset_subordinate
>
> Prior to this patch, an example kernel message may show something like:
>
> pcieport 0000:50:01.0: pciehp: Slot(40): Link Down
>
> With this change, the pciehp driver ignores the link event during the
> reset, so may show this message instead:
>
> pcieport 0000:50:01.0: pciehp: Slot(40): Link Down/Up ignored
>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
> drivers/pci/pci-sysfs.c | 3 +-
> drivers/pci/pci.c | 86 +++++++++++++++++++++++++++--------------
> drivers/pci/pci.h | 2 +-
> 3 files changed, 60 insertions(+), 31 deletions(-)
>
> diff --git a/drivers/pci/pci-sysfs.c b/drivers/pci/pci-sysfs.c
> index b44e884fd5372..6187b0f3e2833 100644
> --- a/drivers/pci/pci-sysfs.c
> +++ b/drivers/pci/pci-sysfs.c
> @@ -553,7 +553,6 @@ static ssize_t reset_subordinate_store(struct device *dev,
> const char *buf, size_t count)
> {
> struct pci_dev *pdev = to_pci_dev(dev);
> - struct pci_bus *bus = pdev->subordinate;
> unsigned long val;
>
> if (!capable(CAP_SYS_ADMIN))
> @@ -563,7 +562,7 @@ static ssize_t reset_subordinate_store(struct device *dev,
> return -EINVAL;
>
> if (val) {
> - int ret = pci_try_reset_bus(bus);
> + int ret = pci_try_reset_bridge(pdev);
>
> if (ret)
> return ret;
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 5ab0b22dc7274..c535cd7f45013 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -54,6 +54,10 @@ unsigned int pci_pm_d3hot_delay;
>
> static void pci_pme_list_scan(struct work_struct *work);
>
> +#define PCI_RESET_RESTORE true
> +#define PCI_RESET_NO_RESTORE false
> +static int pci_reset_bridge(struct pci_dev *bridge, bool restore);
As this forward declaration is unnecessary after the suggestion below,
there should be comment before defines to indicate they relate to
pci_reset_bridge()'s restore parameter.
> +
> static LIST_HEAD(pci_pme_list);
> static DEFINE_MUTEX(pci_pme_list_mutex);
> static DECLARE_DELAYED_WORK(pci_pme_work, pci_pme_list_scan);
> @@ -5600,36 +5604,10 @@ static int pci_bus_reset(struct pci_bus *bus, bool probe)
> /**
> * pci_bus_error_reset - reset the bridge's subordinate bus
> * @bridge: The parent device that connects to the bus to reset
> - *
> - * This function will first try to reset the slots on this bus if the method is
> - * available. If slot reset fails or is not available, this will fall back to a
> - * secondary bus reset.
> */
> int pci_bus_error_reset(struct pci_dev *bridge)
> {
> - struct pci_bus *bus = bridge->subordinate;
> - struct pci_slot *slot;
> -
> - if (!bus)
> - return -ENOTTY;
> -
> - mutex_lock(&pci_slot_mutex);
> - if (list_empty(&bus->slots))
> - goto bus_reset;
> -
> - list_for_each_entry(slot, &bus->slots, list)
> - if (pci_probe_reset_slot(slot))
> - goto bus_reset;
> -
> - list_for_each_entry(slot, &bus->slots, list)
> - if (pci_slot_reset(slot, PCI_RESET_DO_RESET))
> - goto bus_reset;
> -
> - mutex_unlock(&pci_slot_mutex);
> - return 0;
> -bus_reset:
> - mutex_unlock(&pci_slot_mutex);
> - return pci_bus_reset(bridge->subordinate, PCI_RESET_DO_RESET);
> + return pci_reset_bridge(bridge, PCI_RESET_NO_RESTORE);
> }
I think this should be moved down below pci_reset_bridge() and the forward
declaration of pci_reset_bridge() removed.
> /**
> @@ -5650,7 +5628,7 @@ EXPORT_SYMBOL_GPL(pci_probe_reset_bus);
> *
> * Same as above except return -EAGAIN if the bus cannot be locked
> */
> -int pci_try_reset_bus(struct pci_bus *bus)
> +static int pci_try_reset_bus(struct pci_bus *bus)
> {
> int rc;
>
> @@ -5670,6 +5648,58 @@ int pci_try_reset_bus(struct pci_bus *bus)
> return rc;
> }
>
> +/**
> + * pci_reset_bridge - reset a bridge's subordinate bus
> + * @bridge: bridge that connects to the bus to reset
> + * @restore: true if affected device states need to be restored after the reset
> + *
> + * This function will first try to reset the slots on this bus if the method is
> + * available. If slot reset fails or is not available, this will fall back to a
> + * secondary bus reset.
> + */
> +static int pci_reset_bridge(struct pci_dev *bridge, bool restore)
> +{
> + struct pci_bus *bus = bridge->subordinate;
> + struct pci_slot *slot;
> +
> + if (!bus)
> + return -ENOTTY;
> +
> + mutex_lock(&pci_slot_mutex);
> + if (list_empty(&bus->slots))
> + goto bus_reset;
> +
> + list_for_each_entry(slot, &bus->slots, list)
> + if (pci_probe_reset_slot(slot))
> + goto bus_reset;
> +
> + list_for_each_entry(slot, &bus->slots, list) {
> + int ret;
> +
> + if (restore)
> + ret = pci_try_reset_slot(slot);
> + else
> + ret = pci_slot_reset(slot, PCI_RESET_DO_RESET);
> +
> + if (ret)
> + goto bus_reset;
> + }
> +
> + mutex_unlock(&pci_slot_mutex);
> + return 0;
> +bus_reset:
> + mutex_unlock(&pci_slot_mutex);
> +
> + if (restore)
> + return pci_try_reset_bus(bus);
> + return pci_bus_reset(bridge->subordinate, PCI_RESET_DO_RESET);
> +}
> +
> +int pci_try_reset_bridge(struct pci_dev *bridge)
> +{
> + return pci_reset_bridge(bridge, PCI_RESET_RESTORE);
> +}
> +
> /**
> * pci_reset_bus - Try to reset a PCI bus
> * @pdev: top level PCI device to reset via slot/bus
> diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
> index d1350d54b932d..9e363ad22e161 100644
> --- a/drivers/pci/pci.h
> +++ b/drivers/pci/pci.h
> @@ -231,7 +231,7 @@ bool pci_reset_supported(struct pci_dev *dev);
> void pci_init_reset_methods(struct pci_dev *dev);
> int pci_bridge_secondary_bus_reset(struct pci_dev *dev);
> int pci_bus_error_reset(struct pci_dev *dev);
> -int pci_try_reset_bus(struct pci_bus *bus);
> +int pci_try_reset_bridge(struct pci_dev *bridge);
>
> struct pci_cap_saved_data {
> u16 cap_nr;
>
--
i.
next prev parent reply other threads:[~2026-02-13 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 22:41 [PATCHv4 0/3] pci slot reset handling fixes Keith Busch
2026-02-12 22:41 ` [PATCHv4 1/3] pci: rename __pci_bus_reset and __pci_slot_reset Keith Busch
2026-02-12 22:41 ` [PATCHv4 2/3] pci: allow all bus devices to use the same slot Keith Busch
2026-02-13 7:26 ` Ilpo Järvinen
2026-02-13 14:10 ` Keith Busch
2026-02-13 7:27 ` Ilpo Järvinen
2026-02-12 22:41 ` [PATCHv4 3/3] pci: make reset_subordinate hotplug safe Keith Busch
2026-02-13 3:41 ` dan.j.williams
2026-02-13 7:32 ` Ilpo Järvinen [this message]
2026-02-13 14:34 ` 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=04516225-9967-fd1e-c756-6963719aa08d@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=alex@shazbot.org \
--cc=dan.j.williams@intel.com \
--cc=helgaas@kernel.org \
--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