AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: "Christian König" <christian.koenig@amd.com>,
	"xinhui pan" <xinhui.pan@amd.com>,
	amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com
Subject: Re: [PATCH] drm/amdgpu: Fix double free of dmabuf
Date: Fri, 19 Nov 2021 11:16:49 -0500	[thread overview]
Message-ID: <474bda10-e97c-b572-9287-da35d8bd7f44@amd.com> (raw)
In-Reply-To: <f56cbf03-6447-7774-1914-6fd19fe75dde@amd.com>

I'm pretty sure I needed this dma_buf_put to avoid a memory leak. I will
double check later today.

Regards,
  Felix


Am 2021-11-19 um 5:52 a.m. schrieb Christian König:
> Am 19.11.21 um 11:17 schrieb xinhui pan:
>> amdgpu_amdkfd_gpuvm_free_memory_of_gpu drop dmabuf reference
>> increased in
>> amdgpu_gem_prime_export.
>> amdgpu_bo_destroy drop dmabuf reference increased in
>> amdgpu_gem_prime_import.
>>
>> So remove this extra dma_buf_put to avoid double free.
>>
>> Signed-off-by: xinhui pan <xinhui.pan@amd.com>
>
> Yeah, Felix pinged me as well that the DMA-buf import code looks odd
> and he is dropping the extra reference which didn't made much sense to
> me.
>
> Acked-by: Christian König <christian.koenig@amd.com> for this patch
> for now, but I'm going to take another look at this when I have time.
>
> Regards,
> Christian.
>
>> ---
>>   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 6 ------
>>   1 file changed, 6 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
>> index 6c6d5d994b5d..0f68d28e002e 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
>> @@ -665,12 +665,6 @@ kfd_mem_attach_dmabuf(struct amdgpu_device
>> *adev, struct kgd_mem *mem,
>>       if (IS_ERR(gobj))
>>           return PTR_ERR(gobj);
>>   -    /* Import takes an extra reference on the dmabuf. Drop it now to
>> -     * avoid leaking it. We only need the one reference in
>> -     * kgd_mem->dmabuf.
>> -     */
>> -    dma_buf_put(mem->dmabuf);
>> -
>>       *bo = gem_to_amdgpu_bo(gobj);
>>       (*bo)->flags |= AMDGPU_GEM_CREATE_PREEMPTIBLE;
>>       (*bo)->parent = amdgpu_bo_ref(mem->bo);
>

  reply	other threads:[~2021-11-19 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19 10:17 [PATCH] drm/amdgpu: Fix double free of dmabuf xinhui pan
2021-11-19 10:52 ` Christian König
2021-11-19 16:16   ` Felix Kuehling [this message]
2021-11-19 23:22 ` Felix Kuehling

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=474bda10-e97c-b572-9287-da35d8bd7f44@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=xinhui.pan@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