Commit 381bf7ca authored Aug 28, 2012 by Daniel Mack Committed by Miklos Szeredi Sep 03, 2012

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>

parent 8d39d801

fs/fuse/control.c

+2 −2

Original line number	Diff line number	Diff line
		@@ -117,7 +117,7 @@ static ssize_t fuse_conn_max_background_write(struct file *file,
		const char __user *buf,
		size_t count, loff_t *ppos)
		{
		unsigned val;
		unsigned uninitialized_var(val);
		ssize_t ret;

		ret = fuse_conn_limit_write(file, buf, count, ppos, &val,
		@@ -154,7 +154,7 @@ static ssize_t fuse_conn_congestion_threshold_write(struct file *file,
		const char __user *buf,
		size_t count, loff_t *ppos)
		{
		unsigned val;
		unsigned uninitialized_var(val);
		ssize_t ret;

		ret = fuse_conn_limit_write(file, buf, count, ppos, &val,

Admin message