Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH v2 2/2] drm/xe: Add a WARN_ON for NULL job in xe_sync_entry_signal
Date: Mon, 18 Mar 2024 17:03:29 +0000	[thread overview]
Message-ID: <Zfhz4YTXolRatbqN@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240318164342.3094-2-nirmoy.das@intel.com>

On Mon, Mar 18, 2024 at 05:43:42PM +0100, Nirmoy Das wrote:
> Add a warn for NULL job when sync->type is
> DRM_XE_SYNC_TYPE_USER_FENCE. This should be a programming
> error and should never happen so warn and let the kernel crash
> if that ever happens.
> 
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>

Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_sync.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_sync.c b/drivers/gpu/drm/xe/xe_sync.c
> index 02c9577fe418..247505c3478d 100644
> --- a/drivers/gpu/drm/xe/xe_sync.c
> +++ b/drivers/gpu/drm/xe/xe_sync.c
> @@ -255,6 +255,7 @@ void xe_sync_entry_signal(struct xe_sync_entry *sync, struct xe_sched_job *job,
>  			dma_fence_put(fence);
>  		}
>  	} else if (sync->type == DRM_XE_SYNC_TYPE_USER_FENCE) {
> +		XE_WARN_ON(!job);
>  		job->user_fence.used = true;
>  		job->user_fence.addr = sync->addr;
>  		job->user_fence.value = sync->timeline_value;
> -- 
> 2.42.0
> 

  reply	other threads:[~2024-03-18 17:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 16:43 [PATCH v2 1/2] drm/xe: Fix potential integer overflow in page size calculation Nirmoy Das
2024-03-18 16:43 ` [PATCH v2 2/2] drm/xe: Add a WARN_ON for NULL job in xe_sync_entry_signal Nirmoy Das
2024-03-18 17:03   ` Matthew Brost [this message]
2024-03-18 17:41   ` Michal Wajdeczko
2024-03-18 18:41     ` Nirmoy Das
2024-03-20  3:20       ` Lucas De Marchi
2024-03-20 13:07         ` Nirmoy Das
2025-02-10 18:05   ` Upadhyay, Tejas
2025-02-10 18:14     ` Upadhyay, Tejas
2024-03-18 22:50 ` ✓ CI.Patch_applied: success for series starting with [v2,1/2] drm/xe: Fix potential integer overflow in page size calculation Patchwork
2024-03-18 22:50 ` ✓ CI.checkpatch: " Patchwork
2024-03-18 22:51 ` ✓ CI.KUnit: " Patchwork
2024-03-18 23:01 ` ✓ CI.Build: " Patchwork
2024-03-18 23:04 ` ✓ CI.Hooks: " Patchwork
2024-03-18 23:05 ` ✓ CI.checksparse: " Patchwork
2024-03-18 23:27 ` ✓ CI.BAT: " Patchwork

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=Zfhz4YTXolRatbqN@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=nirmoy.das@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