AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Khatri, Sunil" <sukhatri@amd.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
	amd-gfx@lists.freedesktop.org
Cc: Sunil.Khatri@amd.com
Subject: Re: [PATCH] drm/amdgpu: grab a BO reference in vm_lock_done_list.
Date: Fri, 31 Oct 2025 14:09:51 +0530	[thread overview]
Message-ID: <6ffc1416-ae2b-4ab0-a602-a3f6711fa213@amd.com> (raw)
In-Reply-To: <20251031082531.32715-1-christian.koenig@amd.com>

[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]


On 31-10-2025 01:55 pm, Christian König wrote:
> Otherwise it is possible that between dropping the status lock and
> locking the BO that the BO is freed up.
>
> Signed-off-by: Christian König<christian.koenig@amd.com>
> ---
>   drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 8 ++++++--
>   1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> index db66b4232de0..c3dfb949a9b8 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> @@ -484,15 +484,19 @@ int amdgpu_vm_lock_done_list(struct amdgpu_vm *vm, struct drm_exec *exec,
>   	spin_lock(&vm->status_lock);
>   	while (!list_is_head(prev->next, &vm->done)) {
>   		bo_va = list_entry(prev->next, typeof(*bo_va), base.vm_status);
> -		spin_unlock(&vm->status_lock);
>   
>   		bo = bo_va->base.bo;
>   		if (bo) {
> +			amdgpu_bo_ref(bo);
> +			spin_unlock(&vm->status_lock);
> +
>   			ret = drm_exec_prepare_obj(exec, &bo->tbo.base, 1);

Just for my understanding, there is a possibility that a bo is free 
after spin_unlock and we might be using a stale/NULL ptr of bo.  So we 
are taking a reference before releasing the lock to make

sure the bo is valid. Now calling drm_exec_prepare_obj take a recount to 
make sure the bo is always from now on. Reviewed-by: Sunil Khatri 
<sunil.khatri@amd.com>

> +			amdgpu_bo_unref(&bo);
>   			if (unlikely(ret))
>   				return ret;
> +
> +			spin_lock(&vm->status_lock);
>   		}
> -		spin_lock(&vm->status_lock);
>   		prev = prev->next;
>   	}
>   	spin_unlock(&vm->status_lock);

[-- Attachment #2: Type: text/html, Size: 2380 bytes --]

  reply	other threads:[~2025-10-31  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31  8:25 [PATCH] drm/amdgpu: grab a BO reference in vm_lock_done_list Christian König
2025-10-31  8:39 ` Khatri, Sunil [this message]
2025-10-31  8:41   ` Christian König

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=6ffc1416-ae2b-4ab0-a602-a3f6711fa213@amd.com \
    --to=sukhatri@amd.com \
    --cc=Sunil.Khatri@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=ckoenig.leichtzumerken@gmail.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