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
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, david.hunter.linux@gmail.com,
khalid@kernel.org, rubenru09@aol.com,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v3] drm/gud: Use kmalloc_array() instead of kmalloc()
Date: Tue, 7 Oct 2025 10:00:53 +0100 [thread overview]
Message-ID: <d087a2c8-05f6-4fc1-924a-c3a84eae119c@gmail.com> (raw)
In-Reply-To: <bef19ef2-b22d-4adb-9513-b267d0e53330@suse.de>
On 10/7/25 9:58 AM, Thomas Zimmermann wrote:
> Hi
>
> Am 07.10.25 um 10:32 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'
>>
>> Signed-off-by: Mehdi Ben Hadj Khelifa <mehdi.benhadjkhelifa@gmail.com>
>
> Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
>
> As Ruben already acked the previous patch, you should add such acks to
> any later patches. But no need to resend a new iteration now. I'll add
> Ruben's a-b when I merge the patch.
ack,I forgot about that. Thanks for the heads-up.We'll do next time!
> Best regards
> Thomas
Best Regards,
Mehdi Ben Hadj Khelifa
>> ---
>> Changelog:
>>
>> Changes since v2:
>> -Reversed width and height in parameter order.
>> Link:https://lore.kernel.org/all/20250923085144.22582-1-
>> mehdi.benhadjkhelifa@gmail.com/
>> Changes since v1:
>> - Use of width as element count and height as size of element to
>> eliminate the mentionned calculation and overflow issues.
>> Link:https://lore.kernel.org/all/20250922174416.226203-1-
>> 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..c32a798ccadf 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(height, width, GFP_KERNEL);
>> if (!buf)
>> return 0;
>
next prev parent reply other threads:[~2025-10-07 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 8:32 [PATCH v3] drm/gud: Use kmalloc_array() instead of kmalloc() Mehdi Ben Hadj Khelifa
2025-10-07 8:58 ` Thomas Zimmermann
2025-10-07 9:00 ` Mehdi Ben Hadj Khelifa [this message]
2025-10-10 7:32 ` Thomas Zimmermann
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=d087a2c8-05f6-4fc1-924a-c3a84eae119c@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=khalid@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).