From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>,
dri-devel@lists.freedesktop.org, christian.koenig@amd.com,
tursulin@igalia.com, simona.vetter@ffwll.ch, robdclark@gmail.com,
alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 1/6] drm: add DRM_SET_NAME ioctl
Date: Mon, 23 Sep 2024 14:03:09 +0300 [thread overview]
Message-ID: <39ffb244-5264-44ee-9bc9-128d73a87ff2@collabora.com> (raw)
In-Reply-To: <75f56ed0-206a-4e81-9972-38c29a3e20be@collabora.com>
On 9/23/24 13:28, Dmitry Osipenko wrote:
...
>> /**
>> diff --git a/include/uapi/drm/drm.h b/include/uapi/drm/drm.h
>> index 16122819edfe..f5e92e4f909b 100644
>> --- a/include/uapi/drm/drm.h
>> +++ b/include/uapi/drm/drm.h
>> @@ -1024,6 +1024,13 @@ struct drm_crtc_queue_sequence {
>> __u64 user_data; /* user data passed to event */
>> };
>>
>> +#define DRM_NAME_MAX_LEN 64
>
> What about 63, to align data size to 64 bytes including the NULL byte.
On the other hand, the string is copied without NULL byte, so it doesn't
matter.
This leads to another question, why not using strndup_user like it's
done for dma_buf_set_name?
--
Best regards,
Dmitry
next prev parent reply other threads:[~2024-09-24 11:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 9:06 [PATCH v3 0/6] DRM_SET_NAME ioctl Pierre-Eric Pelloux-Prayer
2024-09-20 9:06 ` [PATCH v3 1/6] drm: add " Pierre-Eric Pelloux-Prayer
2024-09-23 10:06 ` Tvrtko Ursulin
2024-09-24 8:22 ` Pierre-Eric Pelloux-Prayer
2024-09-24 8:38 ` Tvrtko Ursulin
2024-09-23 10:28 ` Dmitry Osipenko
2024-09-23 11:03 ` Dmitry Osipenko [this message]
2024-09-23 16:29 ` Pierre-Eric Pelloux-Prayer
2024-09-23 18:09 ` Dmitry Osipenko
2024-09-23 18:18 ` Dmitry Osipenko
2024-09-24 23:28 ` Dmitry Osipenko
2024-09-20 9:06 ` [PATCH v3 2/6] drm: use drm_file name in fdinfo Pierre-Eric Pelloux-Prayer
2024-09-20 9:06 ` [PATCH v3 3/6] drm/amdgpu: delay the use of amdgpu_vm_set_task_info Pierre-Eric Pelloux-Prayer
2024-09-23 10:25 ` Tvrtko Ursulin
2024-09-24 8:23 ` Christian König
2024-09-24 8:43 ` Tvrtko Ursulin
2024-09-24 10:01 ` Pierre-Eric Pelloux-Prayer
2024-09-20 9:06 ` [PATCH v3 4/6] drm/amdgpu: alloc and init vm::task_info from first submit Pierre-Eric Pelloux-Prayer
2024-09-23 10:58 ` Tvrtko Ursulin
2024-09-24 7:21 ` Pierre-Eric Pelloux-Prayer
2024-09-20 9:06 ` [PATCH v3 5/6] drm/amdgpu: make process_name a flexible array Pierre-Eric Pelloux-Prayer
2024-09-20 9:06 ` [PATCH v3 6/6] drm/amdgpu: use drm_file::name in task_info::process_desc Pierre-Eric Pelloux-Prayer
2024-09-20 12:08 ` 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=39ffb244-5264-44ee-9bc9-128d73a87ff2@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=robdclark@gmail.com \
--cc=simona.vetter@ffwll.ch \
--cc=tursulin@igalia.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