From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Miao Xie <miaox@cn.fujitsu.com>, David Sterba <dave@jikos.cz>,
Tsutomu Itoh <t-itoh@jp.fujitsu.com>,
Itaru Kitayama <kitayama@cl.bb4u.ne.jp>,
Linus <torvalds@linux-foundation.org>
Subject: linux-next: build warning from Linus' tree
Date: Fri, 3 Jun 2011 11:10:49 +1000 [thread overview]
Message-ID: <20110603111049.d5967bb3.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Hi all,
With Linus' tree, today's linux-next build (x86_64 allmodconfig) produced
this warning:
fs/btrfs/delayed-inode.c: In function 'btrfs_batch_insert_items':
fs/btrfs/delayed-inode.c:670:6: warning: 'nitems' may be used uninitialized in this function
Introduced by commit 16cdcec736cd ("btrfs: implement delayed inode items
operation"). I think this is a real bug. This variable is not
initialised, only incremented and tested.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
P.S. Chris, time to get a tree into linux-next?
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-06-03 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 1:10 Stephen Rothwell [this message]
2011-06-03 14:17 ` linux-next: build warning from Linus' tree David Sterba
-- strict thread matches above, loose matches on Subject: below --
2021-06-01 7:20 Stephen Rothwell
2021-07-08 2:25 ` Stephen Rothwell
2021-07-20 7:31 ` Stephen Rothwell
2021-08-10 9:29 ` Stephen Rothwell
2019-08-29 22:23 Stephen Rothwell
2019-08-29 22:29 ` Thomas Gleixner
2019-08-30 0:25 ` Stephen Rothwell
2017-02-26 23:23 Stephen Rothwell
2011-06-03 1:00 Stephen Rothwell
2010-10-27 0:29 Stephen Rothwell
2010-10-27 0:58 ` Jesse Gross
2010-10-27 0:00 Stephen Rothwell
2010-09-24 4:08 Stephen Rothwell
2010-09-24 12:32 ` Frederic Weisbecker
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=20110603111049.d5967bb3.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chris.mason@oracle.com \
--cc=dave@jikos.cz \
--cc=kitayama@cl.bb4u.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=t-itoh@jp.fujitsu.com \
--cc=torvalds@linux-foundation.org \
/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).