AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lang Yu <Lang.Yu@amd.com>
To: Felix Kuehling <felix.kuehling@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdkfd: fix kgd_mem memory leak when importing dmabuf
Date: Wed, 27 Jul 2022 09:04:38 +0800	[thread overview]
Message-ID: <YuCPJoVZadAh/a09@lang-desktop> (raw)
In-Reply-To: <007650e0-30e2-88c1-66fe-a942a481515f@amd.com>

On 07/26/ , Felix Kuehling wrote:
> Am 2022-07-26 um 07:15 schrieb Lang Yu:
> > The kgd_mem memory allocated in amdgpu_amdkfd_gpuvm_import_dmabuf()
> > is not freed properly.
> > 
> > Explicitly free it in amdgpu_amdkfd_gpuvm_free_memory_of_gpu()
> > under condition "mem->bo->kfd_bo != mem".
> > 
> > Suggested-by: Felix Kuehling <Felix.Kuehling@amd.com>
> > Signed-off-by: Lang Yu <Lang.Yu@amd.com>
> 
> Some suggestions inline to make the code more readable. Other than that, the
> patch is
> 
> Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
> 
> 
> > ---
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 8 ++++++++
> >   1 file changed, 8 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> > index 6bba6961eee7..086bed40cf34 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> > @@ -1803,6 +1803,7 @@ int amdgpu_amdkfd_gpuvm_free_memory_of_gpu(
> >   		uint64_t *size)
> >   {
> >   	struct amdkfd_process_info *process_info = mem->process_info;
> > +	struct kgd_mem *tmp_mem = mem->bo->kfd_bo;
> 
> Right, you need this because using mem after drm_gem_object_put would be a
> potential use-after-free. Instead of saving this pointer with some obscure
> variable name, you could just save a bool with a more meaningful name. E.g.:
> 
> 	bool use_release_notifier = (mem->bo->kfd_bo == mem);
> 
> This way you have the entire condition in one place, and the variable name
> explains the meaning.

Got it. Thanks!

Regards,
Lang

> 
> >   	unsigned long bo_size = mem->bo->tbo.base.size;
> >   	struct kfd_mem_attachment *entry, *tmp;
> >   	struct bo_vm_reservation_context ctx;
> > @@ -1895,6 +1896,13 @@ int amdgpu_amdkfd_gpuvm_free_memory_of_gpu(
> >   	 */
> >   	drm_gem_object_put(&mem->bo->tbo.base);
> > +	/*
> > +	 * For kgd_mem allocated in amdgpu_amdkfd_gpuvm_import_dmabuf(),
> > +	 * explicitly free it here.
> > +	 */
> > +	if (mem != tmp_mem)
> 
> 	if (!use_release_notifier)
> 		kfree(mem);
> 
> Regards,
>   Felix
> 
> 
> > +		kfree(mem);
> > +
> >   	return ret;
> >   }

      reply	other threads:[~2022-07-27  1:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 11:15 [PATCH] drm/amdkfd: fix kgd_mem memory leak when importing dmabuf Lang Yu
2022-07-26 14:03 ` Felix Kuehling
2022-07-27  1:04   ` Lang Yu [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=YuCPJoVZadAh/a09@lang-desktop \
    --to=lang.yu@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=felix.kuehling@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