From: Lukas Wunner <lukas@wunner.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal
Date: Tue, 18 Jun 2024 18:56:40 +0200 [thread overview]
Message-ID: <ZnG8SHwGbot1JmHn@wunner.de> (raw)
In-Reply-To: <ZnGx8PN6CWGmUC6J@kbusch-mbp.dhcp.thefacebook.com>
On Tue, Jun 18, 2024 at 10:12:32AM -0600, Keith Busch wrote:
> On Tue, Jun 18, 2024 at 12:54:55PM +0200, Lukas Wunner wrote:
> > However starting with v6.3, pci_bridge_wait_for_secondary_bus() is also
> > called on a DPC event. Commit 53b54ad074de ("PCI/DPC: Await readiness
> > of secondary bus after reset"), which introduced that, failed to
> > appreciate that pci_bridge_wait_for_secondary_bus() now needs to hold a
> > reference on the child device because dpc_handler() and pciehp may
> > indeed run concurrently. The commit was backported to v5.10+ stable
> > kernels, so that's the oldest one affected.
>
> Caution on applying this to 5.10 and 5.15 stable branches: they don't
> have the fancy "__free" cleanup you're using here. The newer active
> stables are okay, though.
I'll let Greg & Sasha know when they start applying this to stable
kernels that ced085ef369a is a prerequisite for v5.10-stable and
v5.15-stable. I can rework the patch if they don't want to apply
ced085ef369a to these older versions.
Thanks,
Lukas
next prev parent reply other threads:[~2024-06-18 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 10:54 [PATCH] PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal Lukas Wunner
2024-06-18 11:37 ` Mika Westerberg
2024-06-18 16:12 ` Keith Busch
2024-06-18 16:56 ` Lukas Wunner [this message]
2024-06-26 19:38 ` Keith Busch
2024-07-01 20:26 ` Krzysztof Wilczyński
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=ZnG8SHwGbot1JmHn@wunner.de \
--to=lukas@wunner.de \
--cc=helgaas@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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