From: "Krzysztof Wilczyński" <kwilczynski@kernel.org>
To: Benjamin Block <bblock@linux.ibm.com>
Cc: Niklas Schnelle <schnelle@linux.ibm.com>,
Guangshuo Li <lgs201920130244@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Gerd Bayer <gbayer@linux.ibm.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Fix AB-BA deadlock between remove and SR-IOV sysfs
Date: Tue, 7 Jul 2026 01:05:51 +0900 [thread overview]
Message-ID: <20260706155911.GA2885536@rocinante> (raw)
In-Reply-To: <20260706143653.GB17215@p1gen4-pw042f0m>
Hello,
> > This seems to be a complete duplicate of Ionut Nechita's patch[0] from
> > April. The comments are close enough, but not identical, that I don't
> > think this can really have been created independently.
>
> Yep, +1.
> This is not helpful. We still want the original patchset included (I sent a
> ping a few minutes ago), but then in its complete form with the proper
> authors.
Older patches (include reviews and conversations about the problem) for reference:
- https://lore.kernel.org/linux-pci/20240610220304.3162895-2-kbusch@meta.com/
- https://lore.kernel.org/linux-pci/20240612181625.3604512-1-kbusch@meta.com/
- https://lore.kernel.org/linux-pci/20251030-revert_sriov_lock-v1-0-70f82ade426f@linux.ibm.com/
- https://lore.kernel.org/linux-pci/20251119-revert_sriov_lock-v2-0-ea50eb1e8f96@linux.ibm.com/
- https://lore.kernel.org/linux-pci/20251216-revert_sriov_lock-v3-0-dac4925a7621@linux.ibm.com/
- https://lore.kernel.org/linux-pci/20260214193235.262219-3-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/20260219212648.82606-1-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/20260225202434.18737-1-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/20260228120138.51197-2-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/20260303080903.28693-1-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/20260306082108.17322-1-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/20260308135352.80346-1-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/20260309194920.16459-1-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/20260310074303.17480-1-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/20260318210316.61975-1-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/20260326083534.23602-1-ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/cover.1776755661.git.ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/cover.1776756380.git.ionut.nechita@windriver.com/
- https://lore.kernel.org/linux-pci/cover.1776839248.git.ionut.nechita@windriver.com/
This patch is a no-go, of course, given all the prior work (as far as 2024)
that had been done to fix this problem.
Thank you,
Krzysztof
prev parent reply other threads:[~2026-07-06 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 15:24 [PATCH] PCI: Fix AB-BA deadlock between remove and SR-IOV sysfs Guangshuo Li
2026-07-05 15:49 ` sashiko-bot
2026-07-06 8:16 ` Niklas Schnelle
2026-07-06 14:36 ` Benjamin Block
2026-07-06 16:05 ` Krzysztof Wilczyński [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=20260706155911.GA2885536@rocinante \
--to=kwilczynski@kernel.org \
--cc=bblock@linux.ibm.com \
--cc=bhelgaas@google.com \
--cc=gbayer@linux.ibm.com \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=schnelle@linux.ibm.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