From: Mehdi Ben Hadj Khelifa <mehdi.benhadjkhelifa@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
airlied@gmail.com, simona@ffwll.ch, mingo@kernel.org,
tglx@linutronix.de, jfalempe@redhat.com,
Shuah Khan <skhan@linuxfoundation.org>,
david.hunter.linux@gmail.com, rubenru09@aol.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] drm/gud: Use kmalloc_array() instead of kmalloc()
Date: Tue, 23 Sep 2025 09:20:09 +0100 [thread overview]
Message-ID: <989ace7c-92a3-438e-a0a6-3cbeb46adba6@gmail.com> (raw)
In-Reply-To: <fda2b300-dd91-4357-8cd0-a82347907164@suse.de>
On 9/23/25 8:06 AM, Thomas Zimmermann wrote:
> Hi
>
> Am 23.09.25 um 08:34 schrieb Thomas Zimmermann:
>> cc Ruben
>>
>> Am 22.09.25 um 19:43 schrieb Mehdi Ben Hadj Khelifa:
>>> Replace kmalloc with kmalloc array in drm/gud/gud_pipe.c since the
>>> calculation inside kmalloc is dynamic "width * height" and added
>>> u_char as the size of each element.
>>>
>>> Signed-off-by: Mehdi Ben Hadj Khelifa <mehdi.benhadjkhelifa@gmail.com>
>>> ---
>>> drivers/gpu/drm/gud/gud_pipe.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/gud/gud_pipe.c b/drivers/gpu/drm/gud/
>>> gud_pipe.c
>>> index 8d548d08f127..eeea0cb4c7aa 100644
>>> --- a/drivers/gpu/drm/gud/gud_pipe.c
>>> +++ b/drivers/gpu/drm/gud/gud_pipe.c
>>> @@ -70,7 +70,7 @@ static size_t gud_xrgb8888_to_r124(u8 *dst, const
>>> struct drm_format_info *format
>>> height = drm_rect_height(rect);
>>> len = drm_format_info_min_pitch(format, 0, width) * height;
>>> - buf = kmalloc(width * height, GFP_KERNEL);
>>> + buf = kmalloc_array(width * height, sizeof(u_char), GFP_KERNEL);
>
> u_char is more or less guaranteed to be 8 bit. So what's the point?
i thought it would be more "clean" to have a data type that is of 1 byte
size to use as a reference for the size of each element here.
> There's a potential overflow in width * height. If anything, you want to
> call kmalloc_array(height, width).
This was more apparent to me after i have sent the patch and was waiting
for a reply first. Since my initial though was that width or height
alone couldn't be treated as a reference to "n of elements" or "size of
each element" but your suggestion is more logical since leaving the
calculation width * height in the kmalloc_array would defeat the purpose
of switching from kmalloc to kmalloc_array since dynamic calculation is
still present and overflow is still possible.
I will send a v2 patch shortly changing to your suggestion.
> Best regards
> Thomas
>
Best Regards,
Mehdi Ben Hadj Khelifa
prev parent reply other threads:[~2025-09-23 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 17:43 [PATCH] drm/gud: Use kmalloc_array() instead of kmalloc() Mehdi Ben Hadj Khelifa
2025-09-23 6:34 ` Thomas Zimmermann
2025-09-23 7:06 ` Thomas Zimmermann
2025-09-23 8:20 ` Mehdi Ben Hadj Khelifa [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=989ace7c-92a3-438e-a0a6-3cbeb46adba6@gmail.com \
--to=mehdi.benhadjkhelifa@gmail.com \
--cc=airlied@gmail.com \
--cc=david.hunter.linux@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mingo@kernel.org \
--cc=mripard@kernel.org \
--cc=rubenru09@aol.com \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
--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