From: David Chinner <dgc@sgi.com>
To: Nathan Scott <nathans@sgi.com>
Cc: Jesper Juhl <jesper.juhl@gmail.com>, Meelis Roos <mroos@linux.ee>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: XFS warning in 2.6.18-rc4
Date: Tue, 15 Aug 2006 13:46:25 +1000 [thread overview]
Message-ID: <20060815034625.GW51703024@melbourne.sgi.com> (raw)
In-Reply-To: <20060811095210.I2596458@wobbly.melbourne.sgi.com>
On Fri, Aug 11, 2006 at 09:52:10AM +1000, Nathan Scott wrote:
> On Fri, Aug 11, 2006 at 01:47:43AM +0200, Jesper Juhl wrote:
> > On 10/08/06, Nathan Scott <nathans@sgi.com> wrote:
> > > On Wed, Aug 09, 2006 at 11:04:53PM +0300, Meelis Roos wrote:
> > > > fs/xfs/xfs_bmap.c: In function 'xfs_bmapi':
> > > > fs/xfs/xfs_bmap.c:2662: warning: 'rtx' is used uninitialized in this function
> > >
> > > You have a particularly dense compiler, unfortunately. This code
> > > has always been this way, its just a false cc warning that can be
> > > safely ignored until you upgrade to a fixed compiler (unless I'm
> > > missing something - please enlighten me if so). It does seem to
> > > be the case that there is no way 'rtx' will be used uninitialised
> > > when xfs_rtpick_extent() doesn't fail... no?
> > >
> > Ok, I may be reading something wrong here, but I think the warning is
> > actually not correct.
>
> Thats how I read it too. By "dense" I meant "buggy".
>
> > Or am I missing something ?
>
> Nope, thats my understanding too. The compiler is wrong in this case.
> The only open issue I guess is whether its worh rearranging the code
> to stop people reporting it as a problem... *shrug*.
No, the compiler needs to be fixed. There are other warnings caused by code
exactly like this that have not been fixed because it is an incorrect warning
(e.g. "idx" in bio_alloc_bioset()).
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2006-08-15 3:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 20:04 Meelis Roos
2006-08-09 22:56 ` Nathan Scott
2006-08-10 23:47 ` Jesper Juhl
2006-08-10 23:52 ` Nathan Scott
2006-08-11 0:02 ` Jesper Juhl
2006-08-15 3:46 ` David Chinner [this message]
2006-08-09 23:06 ` Alexey Dobriyan
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=20060815034625.GW51703024@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=nathans@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 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®