From: Jocelyn Falempe <jfalempe@redhat.com>
To: oushixiong1025@163.com
Cc: Javier Martinez Canillas <javierm@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Shixiong Ou <oushixiong@kylinos.cn>
Subject: Re: [PATCH v3] drm/log: Fix division by zero when scale module parameter is 0
Date: Fri, 31 Jul 2026 09:19:26 +0200 [thread overview]
Message-ID: <e50cb7f0-a98c-4bdc-99ff-09ad9c653334@redhat.com> (raw)
In-Reply-To: <20260730014440.66323-1-oushixiong1025@163.com>
On 30/07/2026 03:44, oushixiong1025@163.com wrote:
> From: Shixiong Ou <oushixiong@kylinos.cn>
>
> The scale module parameter can be set to 0 via kernel command line.
> When scale is 0, scaled_font_h and scaled_font_w become 0, causing
> a division by zero in the rows/columns calculation.
>
> Since the scale module parameter is read-only (0444 permissions), it
> cannot be changed at runtime via sysfs. Clamp it to 1 once in
> drm_log_register().
Thanks, it looks good to me
Reviewed-by: Jocelyn Falempe <jfalempe@redhat.com>
>
> Signed-off-by: Shixiong Ou <oushixiong@kylinos.cn>
> ---
> v2->v3:
> Clamp scale once in drm_log_register() instead of introducing a
> drm_log_scale() helper, since scale is read-only at runtime.
>
> v1->v2:
> Introduce a drm_log_scale() helper.
>
> diff --git a/drivers/gpu/drm/clients/drm_log.c b/drivers/gpu/drm/clients/drm_log.c
> index 294b3be1a6b3..46004abd4e61 100644
> --- a/drivers/gpu/drm/clients/drm_log.c
> +++ b/drivers/gpu/drm/clients/drm_log.c
> @@ -424,6 +424,9 @@ void drm_log_register(struct drm_device *dev)
> {
> struct drm_log *new;
>
> + if (!scale)
> + scale = 1;
> +
> new = kzalloc_obj(*new);
> if (!new)
> goto err_warn;
> --
> 2.25.1
>
> No virus found
> Checked by Hillstone Network AntiVirus
>
prev parent reply other threads:[~2026-07-31 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 1:44 oushixiong1025
2026-07-31 7:19 ` Jocelyn Falempe [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=e50cb7f0-a98c-4bdc-99ff-09ad9c653334@redhat.com \
--to=jfalempe@redhat.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=oushixiong1025@163.com \
--cc=oushixiong@kylinos.cn \
--cc=simona@ffwll.ch \
--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
all inboxes | Powered by JetHome®