ocfs2: fix possible uninitialized variable access
authorJoseph Qi <joseph.qi@huawei.com>
Tue, 14 Apr 2015 22:43:33 +0000 (15:43 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Tue, 14 Apr 2015 23:48:58 +0000 (16:48 -0700)
commit023d4ea358494ccfeb37abfe5b0fd01b45a6051c
tree236d2f72d3a72bc60f1cfce95c3448ad194951e2
parent7c01ad8fe7c159d7e1ddbd8e586d4d0dfed7ab3d
ocfs2: fix possible uninitialized variable access

In ocfs2_local_alloc_find_clear_bits and ocfs2_get_dentry, variable
numfound and set may be uninitialized and then used in tracepoint.  In
ocfs2_xattr_block_get and ocfs2_delete_xattr_in_bucket, variable block_off
and xv may be uninitialized and then used in the following logic due to
unchecked return value.

This patch fixes these possible issues.

Signed-off-by: Joseph Qi <joseph.qi@huawei.com>
Cc: Mark Fasheh <mfasheh@suse.com>
Cc: Joel Becker <jlbec@evilplan.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
fs/ocfs2/export.c
fs/ocfs2/localalloc.c
fs/ocfs2/xattr.c