From: Alex Williamson <alex.williamson@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Nishanth Aravamudan <naravamudan@nvidia.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
Amey Narkhede <ameynarkhede03@gmail.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason Gunthorpe <jgg@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Kevin Tian <kevin.tian@intel.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH v3] PCI: account for sysfs-disabled reset in pci_{slot,bus}_resettable()
Date: Mon, 14 Apr 2025 14:15:44 -0600 [thread overview]
Message-ID: <20250414141544.22ebd4c9.alex.williamson@redhat.com> (raw)
In-Reply-To: <20250304234050.GA265524@bhelgaas>
On Tue, 4 Mar 2025 17:40:50 -0600
Bjorn Helgaas <helgaas@kernel.org> wrote:
> On Fri, Feb 07, 2025 at 02:56:00PM -0600, Nishanth Aravamudan wrote:
> > Commit d88f521da3ef ("PCI: Allow userspace to query and set
> > device reset mechanism") added support for userspace to disable reset of
> > specific PCI devices (by echo'ing "" into reset_method) and
> > pci_{slot,bus}_resettable() methods do not check pci_reset_supported()
> > to see if userspace has disabled reset.
The reset_method attribute selects which reset mechanism is available
to pci_reset_function(). It is not intended to interact with the
slot and bus scope reset mechanisms.
> >
> > __pci_reset_bus()
> > -> pci_bus_reset(..., PCI_RESET_PROBE)
> > -> pci_bus_resettable()
> >
> > __pci_reset_slot()
> > -> pci_slot_reset(..., PCI_RESET_PROBE)
> > -> pci_slot_resettable()
> >
> > pci_reset_bus()
> > -> pci_probe_reset_slot()
> > -> pci_slot_reset(..., PCI_RESET_PROBE)
> > -> pci_bus_resettable()
> > if true:
> > __pci_reset_slot()
> > else:
> > __pci_reset_bus()
> >
> > I was able to reproduce this issue with a vfio device passed to a qemu
> > guest, where I had disabled PCI reset via sysfs. Both
> > vfio_pci_ioctl_get_pci_hot_reset_info() and
> > vfio_pci_ioctl_pci_hot_reset() check if either the vdev's slot or bus is
> > not resettable by calling pci_probe_reset_slot(). Before my change, this
> > ends up ignoring the sysfs file contents and vfio-pci happily ends up
> > issuing a reset to that device.
And that's exactly how it's supposed to work, bus and slot resets are
different mechanisms. This change has broken vfio-pci's ability to
perform bus/slot reset for the vast majority of use cases, where the
reset_methods array is empty because we have devices that have no reset
mechanism other than bus reset. This is seen for example in the
trivial case of a multi-function GPU and audio device. We can no
longer perform a bus reset here because audio function has no reset
mechanism[1].
The irony here is that the bus/slot reset is meant to provide resets
when the device does not support function level reset, but now we need
function level reset support in order to perform a bus/slot reset.
This change has been pushed to stable trees and is already beginning to
cause problems:
https://lore.kernel.org/all/808e1111-27b7-f35b-6d5c-5b275e73677b@absolutedigital.net/
Please revert this change with a cc to stable. Thanks,
Alex
[1] Both the GPU and the audio device should report no available reset,
but I suspect we have an ordering problem that function 1 hadn't been
discovered before we probed bus reset on function 0.
> >
> > Add an explicit check of pci_reset_supported() in both
> > pci_slot_resettable() and pci_bus_resettable() to ensure both the reset
> > status and reset execution are both bypassed if an administrator
> > disables it for a device.
> >
> > Fixes: d88f521da3ef ("PCI: Allow userspace to query and set device reset mechanism")
> > Signed-off-by: Nishanth Aravamudan <naravamudan@nvidia.com>
> > Cc: Bjorn Helgaas <bhelgaas@google.com>
> > Cc: Alex Williamson <alex.williamson@redhat.com>
> > Cc: Raphael Norwitz <raphael.norwitz@nutanix.com>
> > Cc: Amey Narkhede <ameynarkhede03@gmail.com>
> > Cc: linux-pci@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
> > Cc: Jason Gunthorpe <jgg@nvidia.com>
> > Cc: Yishai Hadas <yishaih@nvidia.com>
> > Cc: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> > Cc: Kevin Tian <kevin.tian@intel.com>
> > Cc: kvm@vger.kernel.org
>
> Applied to pci/reset for v6.15, thanks!
>
> > ---
> >
> > Changes since v2:
> > - update commit message to include more details
> >
> > Changes since v1:
> > - fix capitalization and ()s
> > - clarify same checks are done in reset path
> >
> > drivers/pci/pci.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> > index 869d204a70a3..738d29375ad3 100644
> > --- a/drivers/pci/pci.c
> > +++ b/drivers/pci/pci.c
> > @@ -5405,6 +5405,8 @@ 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;
> > @@ -5481,6 +5483,8 @@ 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.34.1
> >
>
next prev parent reply other threads:[~2025-04-14 20:15 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 [this message]
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
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=20250414141544.22ebd4c9.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=ameynarkhede03@gmail.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--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=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