From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Chinner <david@fromorbit.com>, xfs-masters@oss.sgi.com
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build warning after merge of the xfs tree
Date: Thu, 4 Mar 2010 11:19:30 +1100 [thread overview]
Message-ID: <20100304111930.86f7cc62.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
Hi Dave,
After merging the xfs tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
fs/xfs/linux-2.6/xfs_aops.c: In function 'xfs_end_io':
fs/xfs/linux-2.6/xfs_aops.c:232: warning: 'error' may be used uninitialized in this function
Introduced by commit 77d7a0c2eeb285c9069e15396703d0cb9690ac50 ("xfs:
Non-blocking inode locking in IO completion").
I can't tell if this is a false positive. If the first two "if"
statement bodies are skipped, then error is tested uninitialised. It is
possible that at least one of them has to be executed.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-03-04 0:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 0:19 Stephen Rothwell [this message]
2010-03-04 0:57 ` [PATCH] Re: linux-next: build warning after merge of the xfs tree Dave Chinner
2010-03-04 16:24 ` Alex Elder
2017-08-31 0:07 Stephen Rothwell
2017-08-31 10:30 ` Brian Foster
2017-08-31 14:57 ` Darrick J. Wong
2017-08-31 15:22 ` Brian Foster
2017-08-31 15:41 ` Darrick J. Wong
2017-08-31 21:32 ` Dave Chinner
2017-10-31 22:42 Stephen Rothwell
2020-01-15 22:12 Stephen Rothwell
2020-01-24 2:47 ` Stephen Rothwell
2020-01-24 4:17 ` Darrick J. Wong
2020-01-16 0:37 Stephen Rothwell
2020-05-08 1:15 Stephen Rothwell
2021-01-24 22:55 Stephen Rothwell
2021-01-25 13:26 ` Brian Foster
2021-01-27 3:14 ` Darrick J. Wong
2021-02-08 12:44 Stephen Rothwell
2021-06-07 0:48 Stephen Rothwell
2021-06-07 1:15 ` Dave Chinner
2024-02-23 4:36 Stephen Rothwell
2024-02-23 6:35 ` Christoph Hellwig
2024-02-23 8:55 ` Mauro Carvalho Chehab
2024-02-23 14:06 ` Christoph Hellwig
2024-02-24 9:07 ` Akira Yokosawa
2024-02-26 10:57 ` Christoph Hellwig
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=20100304111930.86f7cc62.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).