From: Jens Axboe <jens.axboe@oracle.com>
To: Jesse Barnes <jesse.barnes@intel.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>, linux-kernel@vger.kernel.org
Subject: Re: out-of-bounds array index
Date: Thu, 7 Feb 2008 21:01:22 +0100 [thread overview]
Message-ID: <20080207200121.GO15220@kernel.dk> (raw)
In-Reply-To: <200802071128.55935.jesse.barnes@intel.com>
On Thu, Feb 07 2008, Jesse Barnes wrote:
> On Thursday, February 07, 2008 11:21 am Jan Engelhardt wrote:
> > On Feb 7 2008 19:56, Jens Axboe wrote:
> > >Just saw this from gcc:
> > >
> > >drivers/char/drm/i915_drv.c: In function ?i915_suspend?:
> > >drivers/char/drm/i915_drv.c:173: warning: array subscript is above array
> > >bounds
> > > CC [M] drivers/char/drm/i915_dma.o
> > >drivers/char/drm/i915_drv.c: In function ?i915_resume?:
> > >drivers/char/drm/i915_drv.c:220: warning: array subscript is above array
> > >bounds
> > >
> > >It's this code:
> > >
> > > dev_priv->saveGR[0x18] =
> > > i915_read_indexed(VGA_GR_INDEX, VGA_GR_DATA, 0x18);
> > >
> > >which looks legit, since saveGR is
> >
> > It is not legit at all. 0x18 is the 25th position in the array,
> > but it is only 24 big. (Excluding play-hide-and-seek games like
> > allocating more in case of malloc or char *foo[0].)
>
> I think he was saying that the warning was legit. Anyway, my gcc isn't smart
> enough to emit warnings like this, maybe it's time to ugprade...
of course, the reference was to the warning (I do know C and array
indexing 101 :-)
--
Jens Axboe
prev parent reply other threads:[~2008-02-07 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 18:56 out-of-bounds array index Jens Axboe
2008-02-07 19:03 ` Jesse Barnes
2008-02-07 19:15 ` Jesse Barnes
2008-02-07 19:21 ` Jan Engelhardt
2008-02-07 19:28 ` Jesse Barnes
2008-02-07 20:01 ` Jens Axboe [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=20080207200121.GO15220@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=jengelh@computergmbh.de \
--cc=jesse.barnes@intel.com \
--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