gfs2: avoid uninitialized variable warning
authorArnd Bergmann <arnd@arndb.de>
Tue, 26 Jan 2016 18:08:10 +0000 (13:08 -0500)
committerJiri Slaby <jslaby@suse.cz>
Tue, 9 May 2017 06:19:45 +0000 (08:19 +0200)
commit6e33ef16755a6936b6105868e12712ebdaebd7d0
treefda06051f0252b901c1041f74d61174924d7d394
parent81e06f6e802e89047ec35f893cc953fbdc63988e
gfs2: avoid uninitialized variable warning

commit 67893f12e5374bbcaaffbc6e570acbc2714ea884 upstream.

We get a bogus warning about a potential uninitialized variable
use in gfs2, because the compiler does not figure out that we
never use the leaf number if get_leaf_nr() returns an error:

fs/gfs2/dir.c: In function 'get_first_leaf':
fs/gfs2/dir.c:802:9: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized]
fs/gfs2/dir.c: In function 'dir_split_leaf':
fs/gfs2/dir.c:1021:8: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized]

Changing the 'if (!error)' to 'if (!IS_ERR_VALUE(error))' is
sufficient to let gcc understand that this is exactly the same
condition as in IS_ERR() so it can optimize the code path enough
to understand it.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
fs/gfs2/dir.c