[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9830b666-b78c-9794-0d4a-7de31b9fd9b5@redhat.com>
Date: Wed, 18 Jan 2023 20:00:00 +0100
From: Danilo Krummrich <dakr@...hat.com>
To: Christian König <christian.koenig@....com>,
daniel@...ll.ch, airlied@...hat.com, bskeggs@...hat.com,
jason@...kstrand.net, tzimmermann@...e.de, mripard@...nel.org,
corbet@....net
Cc: dri-devel@...ts.freedesktop.org, nouveau@...ts.freedesktop.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH drm-next 02/14] drm/exec: fix memory leak in
drm_exec_prepare_obj()
On 1/18/23 09:51, Christian König wrote:
> That one should probably be squashed into the original patch.
Yes, just wanted to make it obvious for you to pick it up in case you
did not fix it already yourself.
>
> Christian.
>
> Am 18.01.23 um 07:12 schrieb Danilo Krummrich:
>> Don't call drm_gem_object_get() unconditionally.
>>
>> Signed-off-by: Danilo Krummrich <dakr@...hat.com>
>> ---
>> drivers/gpu/drm/drm_exec.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/drm_exec.c b/drivers/gpu/drm/drm_exec.c
>> index ed2106c22786..5713a589a6a3 100644
>> --- a/drivers/gpu/drm/drm_exec.c
>> +++ b/drivers/gpu/drm/drm_exec.c
>> @@ -282,7 +282,6 @@ int drm_exec_prepare_obj(struct drm_exec *exec,
>> struct drm_gem_object *obj,
>> goto error_unlock;
>> }
>> - drm_gem_object_get(obj);
>> return 0;
>> error_unlock:
>
Powered by blists - more mailing lists