linux-kernel - linux-next: build warning after merge of the xfs tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100304111930.86f7cc62.sfr@canb.auug.org.au>
Date:	Thu, 4 Mar 2010 11:19:30 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Dave Chinner <david@...morbit.com>, xfs-masters@....sgi.com
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: linux-next: build warning after merge of the xfs tree

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@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped