mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Dipendra Khadka <kdipendra88@gmail.com>,
	Felix.Kuehling@amd.com, alexander.deucher@amd.com,
	Xinhui.Pan@amd.com, airlied@gmail.com, daniel@ffwll.ch
Cc: amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: drivers/gpu/drm/amd/amdgpu: Fix null pointer deference in amdkfd_fence_get_timeline_name
Date: Fri, 20 Sep 2024 12:16:18 +0200	[thread overview]
Message-ID: <ac13994c-b77b-48f2-b2cf-20299f02c2e8@amd.com> (raw)
In-Reply-To: <20240920090959.30755-1-kdipendra88@gmail.com>

Am 20.09.24 um 11:09 schrieb Dipendra Khadka:
> '''
> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:108:9: error: Null pointer dereference: fence [nullPointer]
>   return fence->timeline_name;
>          ^
> '''
>
> The method to_amdgpu_amdkfd_fence can return NULL incase of empty f
> or f->ops != &amdkfd_fence_ops.Hence, check has been added .
> If fence is null , then null is returned.

Well NAK, completely nonsense. Calling the function with a NULL fence is 
illegal.

Regards,
Christian.

>
> Signed-off-by: Dipendra Khadka <kdipendra88@gmail.com>
> ---
>   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c
> index 1ef758ac5076..2313babcc944 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c
> @@ -105,6 +105,9 @@ static const char *amdkfd_fence_get_timeline_name(struct dma_fence *f)
>   {
>   	struct amdgpu_amdkfd_fence *fence = to_amdgpu_amdkfd_fence(f);
>   
> +	if (!fence)
> +		return NULL;
> +
>   	return fence->timeline_name;
>   }
>   


  reply	other threads:[~2024-09-20 10:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20  9:09 Dipendra Khadka
2024-09-20 10:16 ` Christian König [this message]
2024-09-20 16:31   ` Dipendra Khadka
2024-09-20 18:58     ` Christian König
2024-09-21  4:25       ` Dipendra Khadka
2024-09-23 13:11         ` Christian König
2024-09-23 16:48           ` Dipendra Khadka

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=ac13994c-b77b-48f2-b2cf-20299f02c2e8@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    --cc=kdipendra88@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®