From: Karol Wachowski <karol.wachowski@linux.intel.com>
To: "Christian König" <christian.koenig@amd.com>, David.Francis@amd.com
Cc: felix.kuehling@amd.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, sumit.semwal@linaro.org,
andrzej.kacprowski@linux.intel.com,
maciej.falkowski@linux.intel.com,
dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
linaro-mm-sig@lists.linaro.org, stable@vger.kernel.org
Subject: Re: [PATCH] drm: Fix object leak in DRM_IOCTL_GEM_CHANGE_HANDLE
Date: Fri, 12 Dec 2025 14:21:19 +0100 [thread overview]
Message-ID: <1022011b-fadf-4cca-afab-25a2a41628ea@linux.intel.com> (raw)
In-Reply-To: <e35a9c5d-a09c-4716-959b-2720c72bf383@amd.com>
On 12/12/2025 2:06 PM, Christian König wrote:
> On 12/12/25 14:02, Karol Wachowski wrote:
>> Add missing drm_gem_object_put() call when drm_gem_object_lookup()
>> successfully returns an object. This fixes a GEM object reference
>> leak that can prevent driver modules from unloading when using
>> prime buffers.
>
> Good catch.
>
>> Fixes: 53096728b891 ("drm: Add DRM prime interface to reassign GEM handle")
>> Signed-off-by: Karol Wachowski <karol.wachowski@linux.intel.com>
>
> CC: stable 6.18?
Good idea - added CC: stable in v2.
>
>> ---
>> drivers/gpu/drm/drm_gem.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c
>> index ca1956608261..e150bc1ce65a 100644
>> --- a/drivers/gpu/drm/drm_gem.c
>> +++ b/drivers/gpu/drm/drm_gem.c
>> @@ -1001,7 +1001,7 @@ int drm_gem_change_handle_ioctl(struct drm_device *dev, void *data,
>> {
>> struct drm_gem_change_handle *args = data;
>> struct drm_gem_object *obj;
>> - int ret;
>> + int ret = 0;
>
> Please set ret explicitly in the if branch below.
>
> Always initializing return values is usually considered bad coding style.
Totally agree, moved setting to suggested place in v2.
>
> Apart from that looks good to me.
>
> Thanks,
> Christian.
Thanks,
Karol.>
>>
>> if (!drm_core_check_feature(dev, DRIVER_GEM))
>> return -EOPNOTSUPP;
>> @@ -1011,7 +1011,7 @@ int drm_gem_change_handle_ioctl(struct drm_device *dev, void *data,
>> return -ENOENT;
>>
>> if (args->handle == args->new_handle)
>> - return 0;
>> + goto out;
>>
>> mutex_lock(&file_priv->prime.lock);
>>
>> @@ -1043,6 +1043,8 @@ int drm_gem_change_handle_ioctl(struct drm_device *dev, void *data,
>>
>> out_unlock:
>> mutex_unlock(&file_priv->prime.lock);
>> +out:
>> + drm_gem_object_put(obj);
>>
>> return ret;
>> }
>
prev parent reply other threads:[~2025-12-12 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 13:02 [PATCH] drm: Fix object leak in DRM_IOCTL_GEM_CHANGE_HANDLE Karol Wachowski
2025-12-12 13:06 ` Christian König
2025-12-12 13:21 ` Karol Wachowski [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=1022011b-fadf-4cca-afab-25a2a41628ea@linux.intel.com \
--to=karol.wachowski@linux.intel.com \
--cc=David.Francis@amd.com \
--cc=airlied@gmail.com \
--cc=andrzej.kacprowski@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maciej.falkowski@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).