diff options
| author |   Josef Bacik <josef@toxicpanda.com> | 2019-10-02 10:03:36 -0400 |
|---|---|---|
| committer |   David Sterba <dsterba@suse.com> | 2019-10-03 15:00:56 +0200 |
| commit | c5f4987e86f6692fdb12533ea1fc7a7bb98e555a (patch) | |
| tree | 80dabb48e049292e0246f5200b3934dddc31edd0 /fs | |
| parent | btrfs: allocate new inode in NOFS context (diff) | |
| download | linux-dev-c5f4987e86f6692fdb12533ea1fc7a7bb98e555a.tar.xz linux-dev-c5f4987e86f6692fdb12533ea1fc7a7bb98e555a.zip | |
btrfs: fix uninitialized ret in ref-verify
Coverity caught a case where we could return with a uninitialized value
in ret in process_leaf. This is actually pretty likely because we could
very easily run into a block group item key and have a garbage value in
ret and think there was an errror. Fix this by initializing ret to 0.
Reported-by: Colin Ian King <colin.king@canonical.com>
Fixes: fd708b81d972 ("Btrfs: add a extent ref verify tool")
CC: stable@vger.kernel.org # 4.19+
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs')
| -rw-r--r-- | fs/btrfs/ref-verify.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/btrfs/ref-verify.c b/fs/btrfs/ref-verify.c index e87cbdad02a3..b57f3618e58e 100644 --- a/fs/btrfs/ref-verify.c +++ b/fs/btrfs/ref-verify.c @@ -500,7 +500,7 @@ static int process_leaf(struct btrfs_root *root, struct btrfs_extent_data_ref *dref; struct btrfs_shared_data_ref *sref; u32 count; - int i = 0, tree_block_level = 0, ret; + int i = 0, tree_block_level = 0, ret = 0; struct btrfs_key key; int nritems = btrfs_header_nritems(leaf); |