From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Theodore Ts'o" <tytso@mit.edu>, Akira Fujita <a-fujita@rs.jp.nec.com>
Cc: linux-ext4@vger.kernel.org
Subject: New compiler warning in 2.6.34-rc1: 'start_ext.ee_block' may be used uninitialized
Date: Mon, 15 Mar 2010 15:42:39 +0100 [thread overview]
Message-ID: <4B9E475F.1010302@s5r6.in-berlin.de> (raw)
Hi,
I saw the following scroll by during kernel compilation:
fs/ext4/move_extent.c: In function 'mext_leaf_block':
fs/ext4/move_extent.c:478: warning: 'start_ext.ee_block' may be used
uninitialized in this function
Is it real? It seems that the initial start_ext.ee_len = 0 guards
against accidental use of an uninitialized start_ext.ee_block, but maybe
I missed something.
The message is from gcc (Gentoo 4.3.4 p1.0, pie-10.1.5) 4.3.4 here.
--
Stefan Richter
-=====-==-=- --== -====
http://arcgraph.de/sr/
next reply other threads:[~2010-03-15 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 14:42 Stefan Richter [this message]
2010-03-15 15:41 ` New compiler warning in 2.6.34-rc1: 'start_ext.ee_block' may be used uninitialized tytso
2010-03-25 2:42 ` Akira Fujita
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=4B9E475F.1010302@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=a-fujita@rs.jp.nec.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).