From: Bjorn Helgaas <helgaas@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: naravamudan@nvidia.com, bhelgaas@google.com,
raphael.norwitz@nutanix.com, ameynarkhede03@gmail.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
jgg@nvidia.com, yishaih@nvidia.com,
shameerali.kolothum.thodi@huawei.com, kevin.tian@intel.com,
kvm@vger.kernel.org, cp@absolutedigital.net,
stable@vger.kernel.org
Subject: Re: [PATCH] Revert "PCI: Avoid reset when disabled via sysfs"
Date: Tue, 15 Apr 2025 15:39:29 -0500 [thread overview]
Message-ID: <20250415203929.GA34692@bhelgaas> (raw)
In-Reply-To: <20250414211828.3530741-1-alex.williamson@redhat.com>
On Mon, Apr 14, 2025 at 03:18:23PM -0600, Alex Williamson wrote:
> This reverts commit 479380efe1625e251008d24b2810283db60d6fcd.
>
> The reset_method attribute on a PCI device is only intended to manage
> the availability of function scoped resets for a device. It was never
> intended to restrict resets targeting the bus or slot.
>
> In introducing a restriction that each device must support function
> level reset by testing pci_reset_supported(), we essentially create a
> catch-22, that a device must have a function scope reset in order to
> support bus/slot reset, when we use bus/slot reset to effect a reset
> of a device that does not support a function scoped reset, especially
> multi-function devices.
>
> This breaks the majority of uses cases where vfio-pci uses bus/slot
> resets to manage multifunction devices that do not support function
> scoped resets.
>
> Fixes: 479380efe162 ("PCI: Avoid reset when disabled via sysfs")
> Reported-by: Cal Peake <cp@absolutedigital.net>
> Link: https://lore.kernel.org/all/808e1111-27b7-f35b-6d5c-5b275e73677b@absolutedigital.net
> Cc: stable@vger.kernel.org
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Applied with Kevin's reviewed-by to pci/for-linus for v6.15, thanks,
and sorry for the breakage.
> ---
> drivers/pci/pci.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 4d7c9f64ea24..e77d5b53c0ce 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -5429,8 +5429,6 @@ static bool pci_bus_resettable(struct pci_bus *bus)
> return false;
>
> list_for_each_entry(dev, &bus->devices, bus_list) {
> - if (!pci_reset_supported(dev))
> - return false;
> if (dev->dev_flags & PCI_DEV_FLAGS_NO_BUS_RESET ||
> (dev->subordinate && !pci_bus_resettable(dev->subordinate)))
> return false;
> @@ -5507,8 +5505,6 @@ static bool pci_slot_resettable(struct pci_slot *slot)
> list_for_each_entry(dev, &slot->bus->devices, bus_list) {
> if (!dev->slot || dev->slot != slot)
> continue;
> - if (!pci_reset_supported(dev))
> - return false;
> if (dev->dev_flags & PCI_DEV_FLAGS_NO_BUS_RESET ||
> (dev->subordinate && !pci_bus_resettable(dev->subordinate)))
> return false;
> --
> 2.48.1
>
prev parent reply other threads:[~2025-04-15 20:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 21:52 [PATCH] pci: account for sysfs-disabled reset in pci_{slot,bus}_resettable Nishanth Aravamudan
2025-01-13 20:42 ` Jason Gunthorpe
2025-01-22 18:14 ` Nishanth Aravamudan
2025-01-23 13:33 ` Jason Gunthorpe
2025-01-23 15:14 ` Nishanth Aravamudan
2025-01-13 23:25 ` Bjorn Helgaas
2025-01-22 18:14 ` Nishanth Aravamudan
2025-01-22 19:22 ` [PATCH v2] PCI: account for sysfs-disabled reset in pci_{slot,bus}_resettable() Nishanth Aravamudan
2025-02-07 20:56 ` [PATCH v3] " Nishanth Aravamudan
2025-03-04 23:40 ` Bjorn Helgaas
2025-04-14 20:15 ` Alex Williamson
2025-04-14 21:18 ` [PATCH] Revert "PCI: Avoid reset when disabled via sysfs" Alex Williamson
2025-04-15 6:24 ` Tian, Kevin
2025-04-15 20:39 ` 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=20250415203929.GA34692@bhelgaas \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=ameynarkhede03@gmail.com \
--cc=bhelgaas@google.com \
--cc=cp@absolutedigital.net \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=naravamudan@nvidia.com \
--cc=raphael.norwitz@nutanix.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=stable@vger.kernel.org \
--cc=yishaih@nvidia.com \
/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