From: Dave Jiang <dave.jiang@intel.com>
To: Gregory Price <gourry@gourry.net>, linux-cxl@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
dave@stgolabs.net, jonathan.cameron@huawei.com,
alison.schofield@intel.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, dan.j.williams@intel.com
Subject: Re: [PATCH] cxl/memdev: fix deadlock in cxl_memdev_autoremove() on attach failure
Date: Tue, 10 Feb 2026 09:27:22 -0700 [thread overview]
Message-ID: <bb3e385c-89cd-48e4-9db8-edd04b7736e7@intel.com> (raw)
In-Reply-To: <20260210154320.1748223-1-gourry@gourry.net>
On 2/10/26 8:43 AM, Gregory Price wrote:
> cxl_memdev_autoremove() takes device_lock(&cxlmd->dev) via guard(device)
> and then calls cxl_memdev_unregister() when the attach callback was
> provided but cxl_mem_probe() failed to bind.
>
> cxl_memdev_unregister() calls
> cdev_device_del()
> device_del()
> bus_remove_device()
> device_release_driver()
>
> which also takes device_lock(), deadlocking the calling thread.
>
> This path is reached when a driver uses the @attach parameter to
> devm_cxl_add_memdev() and the CXL topology fails to enumerate (e.g.
> DVSEC range registers decode outside platform-defined CXL ranges,
> causing the endpoint port probe to fail).
>
> Fix by using scoped_guard() and breaking out of the guard scope before
> calling cxl_memdev_unregister(), so device_lock() is released first.
>
> Fixes: 29317f8dc6ed ("cxl/mem: Introduce cxl_memdev_attach for CXL-dependent operation")
> Signed-off-by: Gregory Price <gourry@gourry.net>
Reivewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/cxl/core/memdev.c | 25 ++++++++++++++-----------
> 1 file changed, 14 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/cxl/core/memdev.c b/drivers/cxl/core/memdev.c
> index af3d0cc65138..c0de767b24fb 100644
> --- a/drivers/cxl/core/memdev.c
> +++ b/drivers/cxl/core/memdev.c
> @@ -1098,19 +1098,22 @@ static struct cxl_memdev *cxl_memdev_autoremove(struct cxl_memdev *cxlmd)
> * return. Note that failure here could be the result of a race to
> * teardown the CXL port topology. I.e. cxl_mem_probe() could have
> * succeeded and then cxl_mem unbound before the lock is acquired.
> + *
> + * Check under device_lock but unregister outside of it, as
> + * cxl_memdev_unregister() will also take the device lock.
> */
> - guard(device)(&cxlmd->dev);
> - if (cxlmd->attach && !cxlmd->dev.driver) {
> - cxl_memdev_unregister(cxlmd);
> - return ERR_PTR(-ENXIO);
> + scoped_guard(device, &cxlmd->dev) {
> + if (cxlmd->attach && !cxlmd->dev.driver)
> + break;
> +
> + rc = devm_add_action_or_reset(cxlmd->cxlds->dev,
> + cxl_memdev_unregister, cxlmd);
> + if (rc)
> + return ERR_PTR(rc);
> + return cxlmd;
> }
> -
> - rc = devm_add_action_or_reset(cxlmd->cxlds->dev, cxl_memdev_unregister,
> - cxlmd);
> - if (rc)
> - return ERR_PTR(rc);
> -
> - return cxlmd;
> + cxl_memdev_unregister(cxlmd);
> + return ERR_PTR(-ENXIO);
> }
>
> /*
next prev parent reply other threads:[~2026-02-10 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 15:43 [PATCH] cxl/memdev: fix deadlock in cxl_memdev_autoremove() on attach failure Gregory Price
2026-02-10 16:27 ` Dave Jiang [this message]
2026-02-10 19:44 ` Ira Weiny
2026-02-10 22:46 ` Gregory Price
2026-02-10 23:20 ` Dave Jiang
2026-02-11 0:05 ` Gregory Price
2026-02-10 23:18 ` dan.j.williams
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=bb3e385c-89cd-48e4-9db8-edd04b7736e7@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=gourry@gourry.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=kernel-team@meta.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishal.l.verma@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