From: Bjorn Helgaas <helgaas@kernel.org>
To: "Ionut Nechita (Wind River)" <ionut.nechita@windriver.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
sebott@linux.ibm.com, schnelle@linux.ibm.com,
bblock@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 15:13:12 -0500 [thread overview]
Message-ID: <20260521201312.GA182641@bhelgaas> (raw)
In-Reply-To: <cover.1776839248.git.ionut.nechita@windriver.com>
On Wed, Apr 22, 2026 at 09:32:40AM +0300, Ionut Nechita (Wind River) wrote:
> Hi Bjorn,
>
> This is v14 of the fix for the SR-IOV race between driver .remove()
> and concurrent hotplug events.
Thanks for your persistence on this!
Can you take a look at the sashiko feedback and see whether there's
any merit to it?
https://sashiko.dev/#/patchset/cover.1776839248.git.ionut.nechita%40windriver.com
next prev parent reply other threads:[~2026-05-21 20:13 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 ` [PATCH v14 0/2] PCI/IOV: Fix SR-IOV locking races and AB-BA deadlock Benjamin Block
2026-05-21 20:13 ` Bjorn Helgaas [this message]
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=20260521201312.GA182641@bhelgaas \
--to=helgaas@kernel.org \
--cc=alifm@linux.ibm.com \
--cc=bblock@linux.ibm.com \
--cc=bhelgaas@google.com \
--cc=dtatulea@nvidia.com \
--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=sebott@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®