Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Bommu Krishnaiah <krishnaiah.bommu@intel.com>,
	intel-xe@lists.freedesktop.org
Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>,
	Tejas Upadhyay <tejas.upadhyay@intel.com>
Subject: Re: [PATCH] drm/xe/ xe_sync: Check NULL before dereferencing
Date: Fri, 22 Mar 2024 09:36:26 +0100	[thread overview]
Message-ID: <0e5793b5-3960-426e-96c8-4789337cf31d@linux.intel.com> (raw)
In-Reply-To: <20231206223027.46588-1-krishnaiah.bommu@intel.com>


On 12/6/2023 11:30 PM, Bommu Krishnaiah wrote:
> checking null pointer before dereferencing schedule job
>
> Signed-off-by: Bommu Krishnaiah <krishnaiah.bommu@intel.com>
> Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> Cc: Tejas Upadhyay <tejas.upadhyay@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_sync.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_sync.c b/drivers/gpu/drm/xe/xe_sync.c
> index 02c9577fe418..3b977061bf9f 100644
> --- a/drivers/gpu/drm/xe/xe_sync.c
> +++ b/drivers/gpu/drm/xe/xe_sync.c
> @@ -255,6 +255,9 @@ 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) {
> +		if (!job)
> +			drm_err(&sync->ufence->xe->drm, "No schedule job fond\n");

Looks like we are working on the same goal, I have sent 
https://patchwork.freedesktop.org/series/131371/ to for this.

Please review that instead.


Regards,

Nirmoy

> +
>   		job->user_fence.used = true;
>   		job->user_fence.addr = sync->addr;
>   		job->user_fence.value = sync->timeline_value;

  parent reply	other threads:[~2024-03-22  8:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 22:30 [PATCH] drm/xe/ xe_sync: Check NULL before dereferencing Bommu Krishnaiah
2024-03-22  8:28 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-22  8:29 ` ✓ CI.checkpatch: " Patchwork
2024-03-22  8:29 ` ✓ CI.KUnit: " Patchwork
2024-03-22  8:36 ` Nirmoy Das [this message]
2024-03-22  8:40 ` ✓ CI.Build: " Patchwork
2024-03-22  8:43 ` ✓ CI.Hooks: " Patchwork
2024-03-22  8:44 ` ✓ CI.checksparse: " Patchwork
2024-03-22  9:10 ` ✓ 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=0e5793b5-3960-426e-96c8-4789337cf31d@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=krishnaiah.bommu@intel.com \
    --cc=tejas.upadhyay@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