From: Dave Chinner <david@fromorbit.com>
To: xfs-masters@oss.sgi.com
Cc: Ingo Molnar <mingo@elte.hu>, 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] linux-next: arm allmodconfig
Date: Wed, 29 Oct 2008 18:40:32 +1100 [thread overview]
Message-ID: <20081029074032.GI4985@disturbed> (raw)
In-Reply-To: <20081028175604.81c31cea.akpm@linux-foundation.org>
On Tue, Oct 28, 2008 at 05:56:04PM -0700, Andrew Morton wrote:
> > fs/xfs/quota/xfs_qm_syscalls.c: In function `xfs_qm_dqrele_inodes_ag':
> > fs/xfs/quota/xfs_qm_syscalls.c:1039: warning: 'inode_refed' might be used uninitialized in this function
I haven't seen this one before. And it's a real bug, too.
gcc-4.3.1 on x86_64 is not picking this warning up:
$ gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.1-9' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-cld --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.3.1 (Debian 4.3.1-9)
$
$
$ touch fs/xfs/quota/xfs_qm_syscalls.c
$ make -j2 ARCH=um
SYMLINK arch/um/include/shared/kern_constants.h
make[1]: `arch/um/sys-x86_64/user-offsets.s' is up to date.
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
CC fs/xfs/quota/xfs_qm_syscalls.o
LD fs/xfs/xfs.o
LD fs/xfs/built-in.o
LD fs/built-in.o
What compiler version are you using?
I'll send out a patch to fix this in a minute.
> > 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....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-10-29 7:40 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 ` Dave Chinner [this message]
2008-10-29 8:24 ` [xfs-masters] " Ingo Molnar
2008-10-29 22:07 ` [xfs-masters] " Dave Chinner
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=20081029074032.GI4985@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=mingo@elte.hu \
--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).