From: Keith Busch <kbusch@kernel.org>
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: Lukas Wunner <lukas@wunner.de>,
"Ionut Nechita (Wind River)" <ionut.nechita@windriver.com>,
linux-pci@vger.kernel.org, helgaas@kernel.org,
sebott@linux.ibm.com, bblock@linux.ibm.com, alifm@linux.ibm.com,
julianr@linux.ibm.com, dtatulea@nvidia.com, mani@kernel.org,
ionut_n2001@yahoo.com, sunlightlinux@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/1] PCI/IOV: Add reentrant locking in sriov_add_vfs/sriov_del_vfs for complete serialization
Date: Tue, 3 Mar 2026 13:02:01 -0700 [thread overview]
Message-ID: <aac-OfCmrp7tmDed@kbusch-mbp> (raw)
In-Reply-To: <286d0488aa72b1741f93f900fd5db5c4334a6f50.camel@linux.ibm.com>
On Tue, Mar 03, 2026 at 08:56:24PM +0100, Niklas Schnelle wrote:
> On Tue, 2026-03-03 at 20:28 +0100, Lukas Wunner wrote:
> > Actually, scratch this particular comment. The deadlock in pciehp
> > is actually an AB-BA deadlock, not recursive acquisition.
>
> Hi Lukas,
>
> Do you have a link to a report or a lockdep splat for this issue?
https://lore.kernel.org/all/4c882e25194ba8282b78fe963fec8faae7cf23eb.1529173804.git.lukas@wunner.de/
prev parent reply other threads:[~2026-03-03 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 8:09 [PATCH v5 0/1] PCI/IOV: Add reentrant locking in sriov_add_vfs/sriov_del_vfs Ionut Nechita (Wind River)
2026-03-03 8:09 ` [PATCH v5 1/1] PCI/IOV: Add reentrant locking in sriov_add_vfs/sriov_del_vfs for complete serialization Ionut Nechita (Wind River)
2026-03-03 18:19 ` Lukas Wunner
2026-03-03 19:28 ` Lukas Wunner
2026-03-03 19:56 ` Niklas Schnelle
2026-03-03 20:02 ` Keith Busch [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=aac-OfCmrp7tmDed@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=alifm@linux.ibm.com \
--cc=bblock@linux.ibm.com \
--cc=dtatulea@nvidia.com \
--cc=helgaas@kernel.org \
--cc=ionut.nechita@windriver.com \
--cc=ionut_n2001@yahoo.com \
--cc=julianr@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mani@kernel.org \
--cc=schnelle@linux.ibm.com \
--cc=sebott@linux.ibm.com \
--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