summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/ctree.h
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2019-06-17 13:07:28 +0200
committerDavid Sterba <dsterba@suse.com>2019-07-02 12:30:49 +0200
commit6c64460cdc8be5fa074aa8fe2ae8736d5792bdc5 (patch)
tree8bb242da4125bce1d017f6045d60e608e2c62c15 /fs/btrfs/ctree.h
parent9e967495e0e0ae8bb08f52aa71b29affc7075d31 (diff)
downloadlinux-6c64460cdc8be5fa074aa8fe2ae8736d5792bdc5.tar.gz
linux-6c64460cdc8be5fa074aa8fe2ae8736d5792bdc5.tar.bz2
linux-6c64460cdc8be5fa074aa8fe2ae8736d5792bdc5.zip
btrfs: shut up bogus -Wmaybe-uninitialized warning
gcc sometimes can't determine whether a variable has been initialized when both the initialization and the use are conditional: fs/btrfs/props.c: In function 'inherit_props': fs/btrfs/props.c:389:4: error: 'num_bytes' may be used uninitialized in this function [-Werror=maybe-uninitialized] btrfs_block_rsv_release(fs_info, trans->block_rsv, This code is fine. Unfortunately, I cannot think of a good way to rephrase it in a way that makes gcc understand this, so I add a bogus initialization the way one should not. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Reviewed-by: David Sterba <dsterba@suse.com> [ gcc 8 and 9 don't emit the warning ] Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/ctree.h')
0 files changed, 0 insertions, 0 deletions