btrfs: fix uninitialized variable in find_first_clear_extent_bit

josefbacik · kdave · commit 26df39a9e5a8 · 2022-12-05T18:00:59.000+01:00
This was caught when syncing extent-io-tree.c into btrfs-progs.  This
however isn't really a problem, the only way next would be uninitialized
is if we found the range we were looking for, and in this case we don't
care about next.  However it's a compile error, so fix it up.

Signed-off-by: Josef Bacik &lt;josef@toxicpanda.com&gt;
Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;
diff --git a/fs/btrfs/extent-io-tree.c b/fs/btrfs/extent-io-tree.c
@@ -1425,7 +1425,7 @@ void find_first_clear_extent_bit(struct extent_io_tree *tree, u64 start,
 				 u64 *start_ret, u64 *end_ret, u32 bits)
 {
 	struct extent_state *state;
-	struct extent_state *prev = NULL, *next;
+	struct extent_state *prev = NULL, *next = NULL;
 
 	spin_lock(&tree->lock);
 

Original file line number	Diff line number	Diff line change
`@@ -1425,7 +1425,7 @@ void find_first_clear_extent_bit(struct extent_io_tree *tree, u64 start,`
`1425`	`1425`	`u64 start_ret, u64 end_ret, u32 bits)`
`1426`	`1426`	`{`
`1427`	`1427`	`struct extent_state *state;`
`1428`		`- struct extent_state prev = NULL, next;`
	`1428`	`+ struct extent_state prev = NULL, next = NULL;`
`1429`	`1429`
`1430`	`1430`	`spin_lock(&tree->lock);`
`1431`	`1431`