All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhoucm1 <david1.zhou-5C7GfCeVMHo@public.gmane.org>
To: "Christian König"
	<deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>,
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	Ken.Wang-5C7GfCeVMHo@public.gmane.org
Subject: Re: [PATCH] drm/amdgpu: fix memory leak in wait_all_fence
Date: Fri, 7 Apr 2017 17:03:57 +0800	[thread overview]
Message-ID: <58E755FD.1080501@amd.com> (raw)
In-Reply-To: <6aa1afcf-b2d3-ea84-b08c-3520fffb0b7c-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>



On 2017年04月07日 16:55, Christian König wrote:
> Am 07.04.2017 um 10:46 schrieb zhoucm1:
>>
>>
>> On 2017年04月07日 16:36, Christian König wrote:
>>> Am 07.04.2017 um 05:36 schrieb Chunming Zhou:
>>>> Change-Id: Ib3e271e00e49f10152c1b3eace981a6bf78820de
>>>> Signed-off-by: Chunming Zhou <David1.Zhou@amd.com>
>>>
>>> NAK, that will allocate an array for the fence again, which we 
>>> wanted to avoid.
>> I don't got your means, the **array just to store fence temporary, 
>> freed at the end.
>
> Yeah, but that is unnecessary. We created this function to just avoid 
> that.
>
>>
>>>
>>> We should just drop the fence reference directly after waiting for it.
>> How to handle err case in the middle.
>
> just put a fence_put() directly after fence_wait_timeout(). We don't 
> need to keep a reference to the fence till the end.
I see your mean, will send V2 soon.

Regards,
David Zhou
>
> Regards,
> Christian.
>
>>
>> Regards,
>> David Zhou
>>>
>>> Regards,
>>> Christian.
>>>
>>>> ---
>>>>   drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 25 
>>>> +++++++++++++++++++------
>>>>   1 file changed, 19 insertions(+), 6 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c 
>>>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c
>>>> index de1c4c3..d842452 100644
>>>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c
>>>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c
>>>> @@ -1216,22 +1216,28 @@ static int amdgpu_cs_wait_all_fences(struct 
>>>> amdgpu_device *adev,
>>>>                        struct drm_amdgpu_fence *fences)
>>>>   {
>>>>       uint32_t fence_count = wait->in.fence_count;
>>>> +    struct fence **array;
>>>>       unsigned int i;
>>>>       long r = 1;
>>>>   +    array = kcalloc(fence_count, sizeof(struct fence *), 
>>>> GFP_KERNEL);
>>>> +
>>>> +    if (array == NULL)
>>>> +        return -ENOMEM;
>>>>       for (i = 0; i < fence_count; i++) {
>>>>           struct fence *fence;
>>>>           unsigned long timeout = 
>>>> amdgpu_gem_timeout(wait->in.timeout_ns);
>>>>             fence = amdgpu_cs_get_fence(adev, filp, &fences[i]);
>>>> -        if (IS_ERR(fence))
>>>> -            return PTR_ERR(fence);
>>>> -        else if (!fence)
>>>> +        if (IS_ERR(fence)) {
>>>> +            r = PTR_ERR(fence);
>>>> +            goto err;
>>>> +        } else if (!fence)
>>>>               continue;
>>>> -
>>>> +        array[i] = fence;
>>>>           r = kcl_fence_wait_timeout(fence, true, timeout);
>>>>           if (r < 0)
>>>> -            return r;
>>>> +            goto err;
>>>>             if (r == 0)
>>>>               break;
>>>> @@ -1240,7 +1246,14 @@ static int amdgpu_cs_wait_all_fences(struct 
>>>> amdgpu_device *adev,
>>>>       memset(wait, 0, sizeof(*wait));
>>>>       wait->out.status = (r > 0);
>>>>   -    return 0;
>>>> +    r = 0;
>>>> +
>>>> +err:
>>>> +    for (i = 0; i < fence_count; i++)
>>>> +        fence_put(array[i]);
>>>> +    kfree(array);
>>>> +
>>>> +    return r;
>>>>   }
>>>>     /**
>>>
>>>
>>
>> _______________________________________________
>> amd-gfx mailing list
>> amd-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>
>

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2017-04-07  9:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07  3:36 [PATCH] drm/amdgpu: fix memory leak in wait_all_fence Chunming Zhou
     [not found] ` <1491536178-5978-1-git-send-email-David1.Zhou-5C7GfCeVMHo@public.gmane.org>
2017-04-07  6:45   ` 答复: " Wang, Ken
2017-04-07  8:36   ` Christian König
     [not found]     ` <058491a9-73a6-eddf-73fb-aaac066f9b3e-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-04-07  8:46       ` zhoucm1
     [not found]         ` <58E751D5.50707-5C7GfCeVMHo@public.gmane.org>
2017-04-07  8:55           ` Christian König
     [not found]             ` <6aa1afcf-b2d3-ea84-b08c-3520fffb0b7c-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-04-07  9:03               ` zhoucm1 [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=58E755FD.1080501@amd.com \
    --to=david1.zhou-5c7gfcevmho@public.gmane.org \
    --cc=Ken.Wang-5C7GfCeVMHo@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.