From: "Christian König" <christian.koenig@amd.com>
To: "Liang, Prike" <Prike.Liang@amd.com>,
"tursulin@ursulin.net" <tursulin@ursulin.net>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Mohan Marimuthu, Yogesh" <Yogesh.Mohanmarimuthu@amd.com>,
"SHANMUGAM, SRINIVASAN" <SRINIVASAN.SHANMUGAM@amd.com>,
"Khatri, Sunil" <Sunil.Khatri@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 7/9] drm/amdgpu: rework amdgpu_userq_wait_ioctl v2
Date: Thu, 5 Feb 2026 12:14:07 +0100 [thread overview]
Message-ID: <d5788ae2-6ed8-4a80-8682-af2f4cd68d9d@amd.com> (raw)
In-Reply-To: <DS7PR12MB600564F569B67F91D9AA6F59FB9BA@DS7PR12MB6005.namprd12.prod.outlook.com>
On 2/3/26 04:39, Liang, Prike wrote:
>> + ptr = u64_to_user_ptr(wait_info->bo_read_handles);
>> + num_read_bo_handles = wait_info->num_bo_read_handles;
>> + r = drm_gem_objects_lookup(filp, ptr, num_read_bo_handles, &gobj_read);
>> + if (r)
>> + goto free_timeline_points;
>> +
>> + ptr = u64_to_user_ptr(wait_info->bo_write_handles);
>
>
> The gobj_write pointer allocation is missing, and this part also has some error handling issues.
> I’ve drafted an attached patch to address this, which can be added to the end of this series.
>
>> + num_write_bo_handles = wait_info->num_bo_write_handles;
>> + r = drm_gem_objects_lookup(filp, ptr, num_write_bo_handles,
>> + &gobj_write);
The gobj_write pointer is allocated by this call here.
We currently need to clean that up, but drm_gem_objects_lookup() should potentially be changed to do that itself.
Regards,
Christian.
next prev parent reply other threads:[~2026-02-05 11:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 12:51 [PATCH 1/9] drm/amdgpu: lock both VM and BO in amdgpu_gem_object_open Christian König
2026-02-02 12:51 ` [PATCH 2/9] drm/amdgpu: revert to old status lock handling v3 Christian König
2026-02-02 21:50 ` Alex Deucher
2026-02-02 12:51 ` [PATCH 3/9] drm/amdgpu: fix amdgpu_userq_evict Christian König
2026-02-02 22:11 ` Alex Deucher
2026-02-02 12:51 ` [PATCH 4/9] drm/amdgpu: completely rework eviction fence handling Christian König
2026-02-02 22:29 ` Alex Deucher
2026-02-02 12:51 ` [PATCH 5/9] drm/amdgpu: fix eviction fence and userq manager shutdown Christian König
2026-02-02 22:37 ` Alex Deucher
2026-02-05 11:10 ` Christian König
2026-02-02 12:51 ` [PATCH 6/9] drm/amdgpu: fix adding eviction fence Christian König
2026-02-02 22:40 ` Alex Deucher
2026-02-02 12:51 ` [PATCH 7/9] drm/amdgpu: rework amdgpu_userq_wait_ioctl v2 Christian König
2026-02-02 13:37 ` Tvrtko Ursulin
2026-02-03 3:39 ` Liang, Prike
2026-02-05 11:14 ` Christian König [this message]
2026-02-06 12:00 ` Khatri, Sunil
2026-02-02 12:51 ` [PATCH 8/9] drm/amdgpu: make amdgpu_user_wait_ioctl more resilent v2 Christian König
2026-02-02 12:51 ` [PATCH 9/9] drm/amdgpu: annotate eviction fence signaling path Christian König
2026-02-02 21:44 ` [PATCH 1/9] drm/amdgpu: lock both VM and BO in amdgpu_gem_object_open Alex Deucher
2026-02-11 8:47 ` Liang, Prike
2026-02-06 10:21 ` Khatri, Sunil
2026-02-10 14:00 ` Christian König
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=d5788ae2-6ed8-4a80-8682-af2f4cd68d9d@amd.com \
--to=christian.koenig@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Prike.Liang@amd.com \
--cc=SRINIVASAN.SHANMUGAM@amd.com \
--cc=Sunil.Khatri@amd.com \
--cc=Yogesh.Mohanmarimuthu@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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