From: Dave Chinner <david@fromorbit.com>
To: xfs-masters@oss.sgi.com
Cc: Thomas Gleixner <tglx@linutronix.de>,
Dave Airlie <airlied@linux.ie>,
netdev@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk,
Herbert Xu <herbert@gondor.apana.org.au>,
Paul Moore <paul.moore@hp.com>, Takashi Iwai <tiwai@suse.de>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [xfs-masters] Re: linux-next: arm allmodconfig
Date: Thu, 30 Oct 2008 09:07:32 +1100 [thread overview]
Message-ID: <20081029220732.GK4985@disturbed> (raw)
In-Reply-To: <20081029082459.GA6364@elte.hu>
On Wed, Oct 29, 2008 at 09:24:59AM +0100, Ingo Molnar wrote:
>
> * Dave Chinner <david@fromorbit.com> wrote:
>
> > > > fs/xfs/xfs_rtalloc.c: In function `xfs_growfs_rt':
> > > > fs/xfs/xfs_rtalloc.c:1875: warning: 'tp' might be used uninitialized in this function
> >
> > False positive, and I don't get this reported, either.
> >
> > Hold on - the above gcc binary only emits a warning for the
> > xfs_growfs_rt issue when CONFIG_CC_OPTIMIZE_FOR_SIZE=y is set. It
> > still doesn't catch the quota bug, though. This is so fucked up....
>
> FYI, i've got 3 XFS warnings mapped in tip/auto-warnings-next:
>
> earth4:~/tip> gll linus..auto-warnings-next | grep xfs
>
> ec2f37c: work around warning in fs/xfs/xfs_mount.c
Can't say I've ever seen that warning. What gcc version is
generating it?
> 8501db3: work around warning in fs/xfs/xfs_rtalloc.c
Yeah, that's bogus.
> 8077af8: warnings: fix xfs posix acl
Should be fixed in the -next tree.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-10-29 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 0:56 linux-next: arm allmodconfig Andrew Morton
2008-10-29 7:12 ` Takashi Iwai
2008-10-29 7:40 ` [xfs-masters] " Dave Chinner
2008-10-29 8:24 ` Ingo Molnar
2008-10-29 22:07 ` Dave Chinner [this message]
2008-10-29 9:40 ` Russell King - ARM Linux
2008-10-29 16:05 ` Tony Lindgren
2008-10-29 10:16 ` Pekka J Enberg
2008-10-29 13:53 ` Paul Moore
2008-10-29 20:12 ` Paul Moore
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=20081029220732.GK4985@disturbed \
--to=david@fromorbit.com \
--cc=airlied@linux.ie \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=penberg@cs.helsinki.fi \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
--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 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).