From: "Sharma, Shashank" <shashank.sharma@amd.com>
To: Lu Yao <yaolu@kylinos.cn>,
alexander.deucher@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com
Cc: felix.kuehling@amd.com, tvrtko.ursulin@igalia.com,
zhenguo.yin@amd.com, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: Add null pointer check before task_info get and put
Date: Thu, 2 Jan 2025 15:12:15 +0100 [thread overview]
Message-ID: <3c9bd4c3-80cb-4c9f-9658-64283789599c@amd.com> (raw)
In-Reply-To: <20250101015830.63570-1-yaolu@kylinos.cn>
Lgtm, Reviewed-by: Shashank Sharma <shashank.sharma@amd.com>
Regards
Shashank
On 01/01/2025 02:58, Lu Yao wrote:
> This patch add null pointer check for amdgpu_vm_put_task_info and
> amdgpu_vm_get_task_info_vm, because there is only a warning if create
> task_info failed in amdgpu_vm_init.
>
> Fixes: b8f67b9ddf4f ("drm/amdgpu: change vm->task_info handling")
> Signed-off-by: Lu Yao <yaolu@kylinos.cn>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> index c9c48b782ec1..65edd74bd944 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> @@ -2336,7 +2336,8 @@ amdgpu_vm_get_vm_from_pasid(struct amdgpu_device *adev, u32 pasid)
> */
> void amdgpu_vm_put_task_info(struct amdgpu_task_info *task_info)
> {
> - kref_put(&task_info->refcount, amdgpu_vm_destroy_task_info);
> + if (task_info)
> + kref_put(&task_info->refcount, amdgpu_vm_destroy_task_info);
> }
>
> /**
> @@ -2352,7 +2353,7 @@ amdgpu_vm_get_task_info_vm(struct amdgpu_vm *vm)
> {
> struct amdgpu_task_info *ti = NULL;
>
> - if (vm) {
> + if (vm && vm->task_info) {
> ti = vm->task_info;
> kref_get(&vm->task_info->refcount);
> }
prev parent reply other threads:[~2025-01-02 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 1:58 Lu Yao
2025-01-02 14:12 ` Sharma, Shashank [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=3c9bd4c3-80cb-4c9f-9658-64283789599c@amd.com \
--to=shashank.sharma@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko.ursulin@igalia.com \
--cc=yaolu@kylinos.cn \
--cc=zhenguo.yin@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
all inboxes | Powered by JetHome®