diff options
| author | Daniel Mack <[email protected]> | 2012-08-28 10:38:03 +0200 |
|---|---|---|
| committer | Miklos Szeredi <[email protected]> | 2012-09-03 17:44:06 +0200 |
| commit | 381bf7cad9dbce701c618f8942fd35954952ef39 (patch) | |
| tree | 11da5214a5b7325df57028eda31fde3d1739a6db /lib/cpu-notifier-error-inject.c | |
| parent | 8d39d801d64658d7d69e4754f287a71e9f9bbcb8 (diff) | |
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 <[email protected]>
Cc: Brian Foster <[email protected]>
Signed-off-by: Miklos Szeredi <[email protected]>
Diffstat (limited to 'lib/cpu-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions