btrfs: turn on -Wmaybe-uninitialized

We had a recent bug that would have been caught by a newer compiler with
-Wmaybe-uninitialized and would have saved us a month of failing tests
that I didn't have time to investigate.

Reviewed-by: Qu Wenruo <wqu@suse.com>
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>

diff --git a/fs/btrfs/Makefile b/fs/btrfs/Makefile
index 555c962fdad66b66da9ff9698041b65ddbc64d01..460eced3f5bd019581cd510b4697b59b12b30fa9 100644 (file)
--- a/fs/btrfs/Makefile
+++ b/fs/btrfs/Makefile
@@ -11,7 +11,8 @@ condflags := \
        $(call cc-option, -Wunused-but-set-variable)            \
        $(call cc-option, -Wunused-const-variable)              \
        $(call cc-option, -Wpacked-not-aligned)                 \
-       $(call cc-option, -Wstringop-truncation)
+       $(call cc-option, -Wstringop-truncation)                \
+       $(call cc-option, -Wmaybe-uninitialized)
 subdir-ccflags-y += $(condflags)
 # The following turn off the warnings enabled by -Wextra
 subdir-ccflags-y += -Wno-missing-field-initializers