mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Lizhi Hou <lizhi.hou@amd.com>,
	ogabbay@kernel.org, quic_jhugo@quicinc.com,
	dri-devel@lists.freedesktop.org, karol.wachowski@linux.intel.com
Cc: linux-kernel@vger.kernel.org, max.zhen@amd.com, sonal.santan@amd.com
Subject: Re: [PATCH V3 3/3] accel/amdxdna: Fix iommu domain lifetime race during device removal
Date: Fri, 12 Jun 2026 13:26:43 -0500	[thread overview]
Message-ID: <921fb98f-8737-4249-b07c-cafa2a4fdea0@kernel.org> (raw)
In-Reply-To: <20260611055150.3070216-3-lizhi.hou@amd.com>



On 6/11/26 00:51, Lizhi Hou wrote:
> When force_iova mode is enabled, amdxdna_remove() frees xdna->domain. If
> amdxdna_gem_obj_free() is called after device removal, it may attempt to
> access xdna->domain, resulting in a use-after-free.
> 
> Fix the race by adding freeing xdna->domain as a managed release action,
> so its lifetime is managed by DRM and remains valid until all managed
> resources are released.
> 
> Fixes: ece3e8980907 ("accel/amdxdna: Allow forcing IOVA-based DMA via module parameter")
> Signed-off-by: Lizhi Hou <lizhi.hou@amd.com>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
> ---
>   drivers/accel/amdxdna/amdxdna_iommu.c | 43 ++++++++++++++++++---------
>   1 file changed, 29 insertions(+), 14 deletions(-)
> 
> diff --git a/drivers/accel/amdxdna/amdxdna_iommu.c b/drivers/accel/amdxdna/amdxdna_iommu.c
> index eff00131d0f8..4f245b969eef 100644
> --- a/drivers/accel/amdxdna/amdxdna_iommu.c
> +++ b/drivers/accel/amdxdna/amdxdna_iommu.c
> @@ -4,6 +4,7 @@
>    */
>   
>   #include <drm/amdxdna_accel.h>
> +#include <drm/drm_managed.h>
>   #include <linux/iommu.h>
>   #include <linux/iova.h>
>   
> @@ -153,10 +154,30 @@ void amdxdna_iommu_free(struct amdxdna_dev *xdna, size_t size,
>   	free_pages((unsigned long)cpu_addr, get_order(size));
>   }
>   
> +static void amdxdna_cleanup_force_iova(struct drm_device *dev, void *res)
> +{
> +	struct amdxdna_dev *xdna = to_xdna_dev(dev);
> +
> +	if (xdna->domain) {
> +		iommu_detach_group(xdna->domain, xdna->group);
> +		put_iova_domain(&xdna->iovad);
> +		iova_cache_put();
> +		iommu_domain_free(xdna->domain);
> +	}
> +
> +	iommu_group_put(xdna->group);
> +}
> +
> +void amdxdna_iommu_fini(struct amdxdna_dev *xdna)
> +{
> +	if (xdna->group && !xdna->domain)
> +		iommu_group_put(xdna->group);
> +}
> +
>   int amdxdna_iommu_init(struct amdxdna_dev *xdna)
>   {
>   	unsigned long order;
> -	int ret;
> +	int ret = 0;
>   
>   	xdna->group = iommu_group_get(xdna->ddev.dev);
>   	if (!xdna->group || !force_iova)
> @@ -182,8 +203,14 @@ int amdxdna_iommu_init(struct amdxdna_dev *xdna)
>   	if (ret)
>   		goto put_iova;
>   
> +	ret = drmm_add_action(&xdna->ddev, amdxdna_cleanup_force_iova, NULL);
> +	if (ret)
> +		goto detach_group;
> +
>   	return 0;
>   
> +detach_group:
> +	iommu_detach_group(xdna->domain, xdna->group);
>   put_iova:
>   	put_iova_domain(&xdna->iovad);
>   	iova_cache_put();
> @@ -191,20 +218,8 @@ int amdxdna_iommu_init(struct amdxdna_dev *xdna)
>   	iommu_domain_free(xdna->domain);
>   put_group:
>   	iommu_group_put(xdna->group);
> +	xdna->group = NULL;
>   	xdna->domain = NULL;
>   
>   	return ret;
>   }
> -
> -void amdxdna_iommu_fini(struct amdxdna_dev *xdna)
> -{
> -	if (xdna->domain) {
> -		iommu_detach_group(xdna->domain, xdna->group);
> -		put_iova_domain(&xdna->iovad);
> -		iova_cache_put();
> -		iommu_domain_free(xdna->domain);
> -	}
> -
> -	if (xdna->group)
> -		iommu_group_put(xdna->group);
> -}


  reply	other threads:[~2026-06-12 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11  5:51 [PATCH V3 1/3] accel/amdxdna: Fix amdxdna_client " Lizhi Hou
2026-06-11  5:51 ` [PATCH V3 2/3] accel/amdxdna: Fix notifier_wq " Lizhi Hou
2026-06-12 18:26   ` Mario Limonciello
2026-06-11  5:51 ` [PATCH V3 3/3] accel/amdxdna: Fix iommu domain " Lizhi Hou
2026-06-12 18:26   ` Mario Limonciello [this message]
2026-06-12 18:25 ` [PATCH V3 1/3] accel/amdxdna: Fix amdxdna_client " Mario Limonciello
2026-06-29 18:00   ` Lizhi Hou

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=921fb98f-8737-4249-b07c-cafa2a4fdea0@kernel.org \
    --to=superm1@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=karol.wachowski@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.hou@amd.com \
    --cc=max.zhen@amd.com \
    --cc=ogabbay@kernel.org \
    --cc=quic_jhugo@quicinc.com \
    --cc=sonal.santan@amd.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

Powered by JetHome