From: Benjamin Block <bblock@linux.ibm.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org,
"Ionut Nechita (Wind River)" <ionut.nechita@windriver.com>,
helgaas@kernel.org, schnelle@linux.ibm.com, linux@roeck-us.net,
lukas@wunner.de, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, intel-xe@lists.freedesktop.org,
matthew.brost@intel.com, michal.wajdeczko@intel.com,
piotr.piorkowski@intel.com, dtatulea@nvidia.com, mani@kernel.org,
kbusch@kernel.org, lkml@mageta.org, alifm@linux.ibm.com,
julianr@linux.ibm.com, ionut_n2001@yahoo.com,
sunlightlinux@gmail.com
Subject: Re: [PATCH v14 0/2] PCI/IOV: Fix SR-IOV locking races and AB-BA deadlock
Date: Thu, 21 May 2026 16:19:02 +0200 [thread overview]
Message-ID: <20260521141902.GD206464@p1gen4-pw042f0m> (raw)
In-Reply-To: <cover.1776839248.git.ionut.nechita@windriver.com>
Hey Bjorn,
On Wed, Apr 22, 2026 at 09:32:40AM +0300, Ionut Nechita (Wind River) wrote:
> From: Ionut Nechita <ionut.nechita@windriver.com>
>
> This is v14 of the fix for the SR-IOV race between driver .remove()
> and concurrent hotplug events.
>
--8<--
>
> This race has been independently observed by multiple organizations:
> - IBM (s390 platform-generated hot-unplug events racing with
> sriov_del_vfs during PF driver unload)
> - NVIDIA (tested by Dragos Tatulea in earlier versions)
> - Intel (xe driver hitting lockdep warnings and deadlocks when
> calling pci_disable_sriov from .remove)
> - Wind River (original reporter and patch author)
>
> Test environment:
> - Tested on s390 by Benjamin Block and Niklas Schnelle (IBM)
> - Tested on x86_64 with Intel and NVIDIA SR-IOV devices (earlier
> versions)
>
> Based on linux-next (next-20260420).
>
--8<--
>
> Ionut Nechita (Wind River) (2):
> PCI/IOV: Make pci_lock_rescan_remove() reentrant and protect
> sriov_add_vfs/sriov_del_vfs
> PCI: Fix AB-BA deadlock between device_lock and pci_rescan_remove_lock
> in remove_store
>
> drivers/pci/iov.c | 9 +++++----
> drivers/pci/pci-sysfs.c | 30 +++++++++++++++++++++++++++++-
> drivers/pci/probe.c | 18 ++++++++++++++++--
> 3 files changed, 50 insertions(+), 7 deletions(-)
do you think this patchset is ready integration? Or what do you think we'd
still need to do to get there?
This race, and especially those I fix in the follow-on patchset
https://lore.kernel.org/linux-pci/cover.1776868550.git.bblock%40linux.ibm.com/
are pretty painful on s390 with PCI hotplug. It forces us to reboot the
system, since there is no other way to get out of the deadlock.
--
Best Regards, Benjamin Block / Linux on IBM Z Kernel Development
IBM Deutschland Research & Development GmbH / https://www.ibm.com/privacy
Vors. Aufs.-R.: Wolfgang Wendt / Geschäftsführung: David Faller
Sitz der Ges.: Ehningen / Registergericht: AmtsG Stuttgart, HRB 243294
next prev parent reply other threads:[~2026-05-21 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 6:32 Ionut Nechita (Wind River)
2026-04-22 6:32 ` [PATCH v14 1/2] PCI/IOV: Make pci_lock_rescan_remove() reentrant and protect sriov_add_vfs/sriov_del_vfs Ionut Nechita (Wind River)
2026-04-22 6:32 ` [PATCH v14 2/2] PCI: Fix AB-BA deadlock between device_lock and pci_rescan_remove_lock in remove_store Ionut Nechita (Wind River)
2026-05-21 14:19 ` Benjamin Block [this message]
2026-05-21 20:13 ` [PATCH v14 0/2] PCI/IOV: Fix SR-IOV locking races and AB-BA deadlock Bjorn Helgaas
2026-05-22 16:05 ` Benjamin Block
2026-07-06 14:29 ` Benjamin Block
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=20260521141902.GD206464@p1gen4-pw042f0m \
--to=bblock@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=bhelgaas@google.com \
--cc=dtatulea@nvidia.com \
--cc=helgaas@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=ionut.nechita@windriver.com \
--cc=ionut_n2001@yahoo.com \
--cc=julianr@linux.ibm.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkml@mageta.org \
--cc=lukas@wunner.de \
--cc=mani@kernel.org \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=piotr.piorkowski@intel.com \
--cc=schnelle@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=sunlightlinux@gmail.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
all inboxes | Powered by JetHome®