From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rahul Kumar <rk0006818@gmail.com>,
lanzano.alex@gmail.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org, rk0006818@gmail.com
Subject: Re: [PATCH] drm/tiny: Use kmalloc_array() instead of kmalloc()
Date: Tue, 23 Sep 2025 16:51:40 +0300 [thread overview]
Message-ID: <712a27fc6c4060e67b3da58cb8564387b40b5971@intel.com> (raw)
In-Reply-To: <20250923110025.1358920-1-rk0006818@gmail.com>
On Tue, 23 Sep 2025, Rahul Kumar <rk0006818@gmail.com> wrote:
> Documentation/process/deprecated.rst recommends against the use of
> kmalloc with dynamic size calculations due to the risk of overflow and
> smaller allocation being made than the caller was expecting.
>
> Replace kmalloc() with kmalloc_array() in drivers/gpu/drm/tiny/repaper.c
> to make the intended allocation size clearer and avoid potential overflow
> issues.
>
> Signed-off-by: Rahul Kumar <rk0006818@gmail.com>
> ---
> drivers/gpu/drm/tiny/repaper.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/tiny/repaper.c b/drivers/gpu/drm/tiny/repaper.c
> index 5c3b51eb0a97..4d439a2d973a 100644
> --- a/drivers/gpu/drm/tiny/repaper.c
> +++ b/drivers/gpu/drm/tiny/repaper.c
> @@ -535,7 +535,7 @@ static int repaper_fb_dirty(struct drm_framebuffer *fb,
> DRM_DEBUG("Flushing [FB:%d] st=%ums\n", fb->base.id,
> epd->factored_stage_time);
>
> - buf = kmalloc(fb->width * fb->height / 8, GFP_KERNEL);
> + buf = kmalloc_array(fb->width, fb->height / 8, GFP_KERNEL);
That's just not the same thing, though.
BR,
Jani.
> if (!buf) {
> ret = -ENOMEM;
> goto out_exit;
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-09-23 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 11:00 [PATCH] drm/tiny: Use kmalloc_array() instead of kmalloc() Rahul Kumar
2025-09-23 13:51 ` Jani Nikula [this message]
2025-09-24 6:07 ` Rahul Kumar
-- strict thread matches above, loose matches on Subject: below --
2025-10-19 15:12 Mehdi Ben Hadj Khelifa
2025-10-19 14:34 ` Greg KH
2025-10-19 14:47 ` Thomas Zimmermann
2025-10-19 16:03 ` Mehdi Ben Hadj Khelifa
2025-10-20 9:50 ` Jani Nikula
2025-10-20 10:49 ` Thomas Zimmermann
2025-10-20 20:06 ` Shuah Khan
2025-10-20 21:11 ` Mehdi Ben Hadj Khelifa
2025-10-20 20:22 ` Shuah Khan
2025-10-20 20:22 ` Shuah Khan
2025-10-20 22:00 ` Mehdi Ben Hadj Khelifa
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=712a27fc6c4060e67b3da58cb8564387b40b5971@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lanzano.alex@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rk0006818@gmail.com \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.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