linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Kennedy <george.kennedy@oracle.com>
To: "geert@linux-m68k.org >> Geert Uytterhoeven"
	<geert@linux-m68k.org>, Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: [PATCH v2 RESEND 2] video: fbdev: cirrusfb: check pixclock to avoid divide by zero
Date: Mon, 13 Dec 2021 10:29:08 -0500	[thread overview]
Message-ID: <8d91b763-f038-af05-8917-6bec2da186b4@oracle.com> (raw)

Do a sanity check on pixclock value to avoid divide by zero.

If the pixclock value is zero, the cirrusfb driver will round up
pixclock to get the derived frequency as close to maxclock as
possible.

Syzkaller reported a divide error in cirrusfb_check_pixclock.

divide error: 0000 [#1] SMP KASAN PTI
CPU: 0 PID: 14938 Comm: cirrusfb_test Not tainted 5.15.0-rc6 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-2
RIP: 0010:cirrusfb_check_var+0x6f1/0x1260

Call Trace:
  fb_set_var+0x398/0xf90
  do_fb_ioctl+0x4b8/0x6f0
  fb_ioctl+0xeb/0x130
  __x64_sys_ioctl+0x19d/0x220
  do_syscall_64+0x3a/0x80
  entry_SYSCALL_64_after_hwframe+0x44/0xae

Cc: <stable@vger.kernel.org> # 5.4.y
Reported-by: syzkaller <syzkaller@googlegroups.com>
Signed-off-by: George Kennedy<george.kennedy@oracle.com>
Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
Hi Andrew, can you pick this patch up?  Some of the fbdev drivers have
maintainers but the cirrusfb.c is basically orphaned.  I sent this patch
in Oct and again in Dec and no one picked it up.  Geert has reviewed it.
Obviously the original code just crashed so this shouldn't be
controversial.

v2: Geert says that instead of just returning an error, this is supposed
to find a valid pixclock and use that.

RESEND: Added the Reviewed by: and Cc: <stable@vger.kernel.org>

Thank you,
George

  drivers/video/fbdev/cirrusfb.c | 16 ++++++++--------
  1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/drivers/video/fbdev/cirrusfb.c 
b/drivers/video/fbdev/cirrusfb.c
index 93802ab..3d47c34 100644
--- a/drivers/video/fbdev/cirrusfb.c
+++ b/drivers/video/fbdev/cirrusfb.c
@@ -469,7 +469,7 @@ static int cirrusfb_check_mclk(struct fb_info *info, 
long freq)
      return 0;
  }

-static int cirrusfb_check_pixclock(const struct fb_var_screeninfo *var,
+static int cirrusfb_check_pixclock(struct fb_var_screeninfo *var,
                     struct fb_info *info)
  {
      long freq;
@@ -478,9 +478,7 @@ static int cirrusfb_check_pixclock(const struct 
fb_var_screeninfo *var,
      unsigned maxclockidx = var->bits_per_pixel >> 3;

      /* convert from ps to kHz */
-    freq = PICOS2KHZ(var->pixclock);
-
-    dev_dbg(info->device, "desired pixclock: %ld kHz\n", freq);
+    freq = PICOS2KHZ(var->pixclock ? : 1);

      maxclock = cirrusfb_board_info[cinfo->btype].maxclock[maxclockidx];
      cinfo->multiplexing = 0;
@@ -488,11 +486,13 @@ static int cirrusfb_check_pixclock(const struct 
fb_var_screeninfo *var,
      /* If the frequency is greater than we can support, we might be able
       * to use multiplexing for the video mode */
      if (freq > maxclock) {
-        dev_err(info->device,
-            "Frequency greater than maxclock (%ld kHz)\n",
-            maxclock);
-        return -EINVAL;
+        var->pixclock = KHZ2PICOS(maxclock);
+
+        while ((freq = PICOS2KHZ(var->pixclock)) > maxclock)
+            var->pixclock++;
      }
+    dev_dbg(info->device, "desired pixclock: %ld kHz\n", freq);
+
      /*
       * Additional constraint: 8bpp uses DAC clock doubling to allow 
maximum
       * pixel clock
-- 1.8.3.1


                 reply	other threads:[~2021-12-13 15:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8d91b763-f038-af05-8917-6bec2da186b4@oracle.com \
    --to=george.kennedy@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).