fuse: mark variables uninitialized
authorDaniel Mack <zonque@gmail.com>
Tue, 28 Aug 2012 08:38:03 +0000 (10:38 +0200)
committerMiklos Szeredi <mszeredi@suse.cz>
Mon, 3 Sep 2012 15:44:06 +0000 (17:44 +0200)
commit381bf7cad9dbce701c618f8942fd35954952ef39
tree11da5214a5b7325df57028eda31fde3d1739a6db
parent8d39d801d64658d7d69e4754f287a71e9f9bbcb8
fuse: mark variables uninitialized

gcc 4.6.3 complains about uninitialized variables in fs/fuse/control.c:

  CC      fs/fuse/control.o
fs/fuse/control.c: In function 'fuse_conn_congestion_threshold_write':
fs/fuse/control.c:165:29: warning: 'val' may be used uninitialized in this function [-Wuninitialized]
fs/fuse/control.c: In function 'fuse_conn_max_background_write':
fs/fuse/control.c:128:23: warning: 'val' may be used uninitialized in this function [-Wuninitialized]

fuse_conn_limit_write() will always return non-zero unless the &val
is modified, so the warning is misleading. Let the compiler know
about it by marking 'val' with 'uninitialized_var'.

Signed-off-by: Daniel Mack <zonque@gmail.com>
Cc: Brian Foster <bfoster@redhat.com>
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
fs/fuse/control.c