Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	<dri-devel@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>, <stable@vger.kernel.org>,
	<syzbot+622bba18029bcde672e1@syzkaller.appspotmail.com>
Subject: Re: [PATCH 1/2] drm/modes: Avoid divide by zero harder in drm_mode_vrefresh()
Date: Fri, 29 Nov 2024 13:30:17 +0530	[thread overview]
Message-ID: <09913faf-f70f-4deb-bc24-295796c8d0ca@intel.com> (raw)
In-Reply-To: <20241129042629.18280-2-ville.syrjala@linux.intel.com>


On 11/29/2024 9:56 AM, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> drm_mode_vrefresh() is trying to avoid divide by zero
> by checking whether htotal or vtotal are zero. But we may
> still end up with a div-by-zero of vtotal*htotal*...
>
> Cc: stable@vger.kernel.org
> Reported-by: syzbot+622bba18029bcde672e1@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=622bba18029bcde672e1
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>   drivers/gpu/drm/drm_modes.c | 11 +++++++----
>   1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
> index 6ba167a33461..71573b85d924 100644
> --- a/drivers/gpu/drm/drm_modes.c
> +++ b/drivers/gpu/drm/drm_modes.c
> @@ -1287,14 +1287,11 @@ EXPORT_SYMBOL(drm_mode_set_name);
>    */
>   int drm_mode_vrefresh(const struct drm_display_mode *mode)
>   {
> -	unsigned int num, den;
> +	unsigned int num = 1, den = 1;
>   
>   	if (mode->htotal == 0 || mode->vtotal == 0)
>   		return 0;
>   
> -	num = mode->clock;
> -	den = mode->htotal * mode->vtotal;
> -
>   	if (mode->flags & DRM_MODE_FLAG_INTERLACE)
>   		num *= 2;
>   	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
> @@ -1302,6 +1299,12 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
>   	if (mode->vscan > 1)
>   		den *= mode->vscan;
>   
> +	if (check_mul_overflow(mode->clock, num, &num))
> +		return 0;
> +
> +	if (check_mul_overflow(mode->htotal * mode->vtotal, den, &den))

Can mode->htotal * mode->vtotal result in overflow?

and we should add:

if (check_mul_overflow(mode->htotal, mode->vtotal, &prod))
	return 0;

Regards,

Ankit

> +		return 0;
> +
>   	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
>   }
>   EXPORT_SYMBOL(drm_mode_vrefresh);

  reply	other threads:[~2024-11-29  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29  4:26 [PATCH 0/2] drm/modes: Fix div-by-zero in drm_mode_vrefresh() Ville Syrjala
2024-11-29  4:26 ` [PATCH 1/2] drm/modes: Avoid divide by zero harder " Ville Syrjala
2024-11-29  8:00   ` Nautiyal, Ankit K [this message]
2024-11-29 13:07     ` Jani Nikula
2024-11-29  4:26 ` [PATCH 2/2] drm/modes: Fix drm_mode_vrefres() docs Ville Syrjala
2024-11-29 13:08   ` Jani Nikula
2024-11-29  5:13 ` ✗ Fi.CI.CHECKPATCH: warning for drm/modes: Fix div-by-zero in drm_mode_vrefresh() Patchwork
2024-11-29  5:29 ` ✓ i915.CI.BAT: success " Patchwork
2024-11-29  7:33 ` ✗ i915.CI.Full: failure " Patchwork

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=09913faf-f70f-4deb-bc24-295796c8d0ca@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+622bba18029bcde672e1@syzkaller.appspotmail.com \
    --cc=ville.syrjala@linux.intel.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