All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: "Richard Purdie" <rpurdie@rpsys.net>,
	linux-kernel@vger.kernel.org, "Ville Syrjälä" <syrjala@sci.fi>
Subject: Re: drivers/video/aty/atyfb_base.c: array overruns
Date: Sat, 31 Mar 2007 09:23:29 +0800	[thread overview]
Message-ID: <1175304210.4663.2.camel@daplas> (raw)
In-Reply-To: <20070319092246.GI752@stusta.de>

On Mon, 2007-03-19 at 10:22 +0100, Adrian Bunk wrote:
> The Coverity checker spotted the following two array overruns in 
> drivers/video/aty/atyfb_base.c:
> 
> <--  snip  -->
> 
> ...
> static const u32 lt_lcd_regs[] = {
>         CONFIG_PANEL_LG,
>         LCD_GEN_CNTL_LG,
>         DSTN_CONTROL_LG,
>         HFB_PITCH_ADDR_LG,
>         HORZ_STRETCHING_LG,
>         VERT_STRETCHING_LG,
>         0, /* EXT_VERT_STRETCH */
>         LT_GIO_LG,
>         POWER_MANAGEMENT_LG
> };

We can pad this array with zeroes, as a stop-gap measure. Ville, what do
you think?

Tony

> 
> void aty_st_lcd(int index, u32 val, const struct atyfb_par *par)
> {
>         if (M64_HAS(LT_LCD_REGS)) {
>                 aty_st_le32(lt_lcd_regs[index], val, par);
> ...
> }
> ...
> u32 aty_ld_lcd(int index, const struct atyfb_par *par)
> {
>         if (M64_HAS(LT_LCD_REGS)) {
>                 return aty_ld_le32(lt_lcd_regs[index], par);
> ...
> }
> ...
> static int aty_bl_update_status(struct backlight_device *bd)
> {
>         struct atyfb_par *par = class_get_devdata(&bd->class_dev);
>         unsigned int reg = aty_ld_lcd(LCD_MISC_CNTL, par);
> ...
>         aty_st_lcd(LCD_MISC_CNTL, reg, par);
> 
>         return 0;
> }
> ...
> 
> <--  snip  -->
> 
> LCD_MISC_CNTL = 0x14 = 20 > 8
> 
> cu
> Adrian
> 


  reply	other threads:[~2007-03-31  1:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19  9:22 drivers/video/aty/atyfb_base.c: array overruns Adrian Bunk
2007-03-31  1:23 ` Antonino A. Daplas [this message]
2007-03-31 14:25   ` syrjala

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=1175304210.4663.2.camel@daplas \
    --to=adaplas@gmail.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=syrjala@sci.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.