From: Christoph Hellwig <hch@lst.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: xfs-masters@oss.sgi.com,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [xfs-masters] fs/xfs/xfs_mount.c:1483: warning: array subscript is above array bounds
Date: Tue, 5 May 2009 10:23:44 +0200 [thread overview]
Message-ID: <20090505082344.GA21212@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0905051001260.4192@anakin>
On Tue, May 05, 2009 at 10:05:05AM +0200, Geert Uytterhoeven wrote:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/407608/:
> fs/xfs/xfs_mount.c:1483: warning: array subscript is above array bounds
>
> xfs_mod_sb(xfs_trans_t *tp, __int64_t fields)
> {
> xfs_sb_field_t f;
>
> ...
> first = xfs_sb_info[f].offset;
> ...
> }
>
> xfs_sb_field_t is an enum with 47 values.
> xfs_sb_info[] has at least 47 entries.
That's the conclusion I came to. I also see similar bogus warnings in
a couple of other places in a full kernel build (not in xfs).
prev parent reply other threads:[~2009-05-05 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 8:05 fs/xfs/xfs_mount.c:1483: warning: array subscript is above array bounds Geert Uytterhoeven
2009-05-05 8:23 ` Christoph Hellwig [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=20090505082344.GA21212@lst.de \
--to=hch@lst.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs-masters@oss.sgi.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 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.