Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Cc: paulo.r.zanoni@intel.com
Subject: Re: [PATCH] drm/xe: Use dma_fence_chain_free in chain fence unused as a sync
Date: Mon, 29 Jul 2024 09:46:54 +0100	[thread overview]
Message-ID: <c03615b0-4237-4047-8afd-1788507abd08@intel.com> (raw)
In-Reply-To: <20240727012216.2118276-1-matthew.brost@intel.com>

On 27/07/2024 02:22, Matthew Brost wrote:
> A chain fence is uninitialized if not installed in a drm sync obj. Thus
> if xe_sync_entry_cleanup is called and sync->chain_fence is non-NULL the
> proper cleanup is dma_fence_chain_free rather than a dma-fence put.
> 
> Reported-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2411
> Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>

Reviewed-by: Matthew Auld <matthew.auld@intel.com>

Also maybe:
https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2261

> ---
>   drivers/gpu/drm/xe/xe_sync.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_sync.c b/drivers/gpu/drm/xe/xe_sync.c
> index 533246f42256..3aa6270e5dd7 100644
> --- a/drivers/gpu/drm/xe/xe_sync.c
> +++ b/drivers/gpu/drm/xe/xe_sync.c
> @@ -259,7 +259,7 @@ void xe_sync_entry_cleanup(struct xe_sync_entry *sync)
>   	if (sync->fence)
>   		dma_fence_put(sync->fence);
>   	if (sync->chain_fence)
> -		dma_fence_put(&sync->chain_fence->base);
> +		dma_fence_chain_free(sync->chain_fence);
>   	if (sync->ufence)
>   		user_fence_put(sync->ufence);
>   }

      parent reply	other threads:[~2024-07-29  8:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-27  1:22 [PATCH] drm/xe: Use dma_fence_chain_free in chain fence unused as a sync Matthew Brost
2024-07-27  1:26 ` ✓ CI.Patch_applied: success for " Patchwork
2024-07-27  1:27 ` ✓ CI.checkpatch: " Patchwork
2024-07-27  1:28 ` ✓ CI.KUnit: " Patchwork
2024-07-27  1:40 ` ✓ CI.Build: " Patchwork
2024-07-27  1:42 ` ✓ CI.Hooks: " Patchwork
2024-07-27  1:43 ` ✓ CI.checksparse: " Patchwork
2024-07-27  2:04 ` ✓ CI.BAT: " Patchwork
2024-07-27 10:52 ` ✗ CI.FULL: failure " Patchwork
2024-07-29  8:46 ` Matthew Auld [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=c03615b0-4237-4047-8afd-1788507abd08@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=paulo.r.zanoni@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