Skip to contentSkip to conversation

btrfs: Do extra chunk block group mapping check at mount

PATCH In review Qu Wenruo 2 participants 2 messages Jul 2, 2018 Btrfs file system

lore
Share & tools
lore

Qu Wenruo

author
#0 lore raw

PATCH 1/1 btrfs: Do extra chunk block group mapping check at mount

Reported in https://bugzilla.kernel.org/show_bug.cgi?id=199837, if a crafted btrfs with incorrect chunk<->block group mapping, it could leads to a lot of unexpected behavior.

Although the crafted image can be catched by block group item checker added in "[PATCH] btrfs: tree-checker: Verify block_group_item", if one crafted a valid enough block group item which can pass above check but still mismatch with existing chunk, it could cause a lot of undefined behavior.

This patch will add extra chunk<->block group mapping check at mount time, so such problem can be detected early and cause no harm.

---
 fs/btrfs/extent-tree.c | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)
fs/btrfs/extent-tree.c +38 -0
index 3d9fe58c0080..7a11dc76cd6d 100644
@@ -10003,6 +10003,31 @@ btrfs_create_block_group_cache(struct btrfs_fs_info *fs_info,
 	return cache;
 }
 
+static int verify_chunk_block_group_mapping(struct btrfs_fs_info *fs_info,
+					    u64 start, u64 len)
+{
+	struct btrfs_mapping_tree *map_tree = &fs_info->mapping_tree;
+	struct extent_map *em;
+	int ret;
+
+	read_lock(&map_tree->map_tree.lock);
+	em = lookup_extent_mapping(&map_tree->map_tree, start, len);
+	read_unlock(&map_tree->map_tree.lock);
+
+	if (!em) {
+		ret = -ENOENT;
+		goto out;
+	}
+	if (em->start != start || em->len != len) {
+		ret = -ENOENT;
+		goto out;
+	}
+	ret = 0;
+out:
+	free_extent_map(em);
+	return ret;
+}
+
 int btrfs_read_block_groups(struct btrfs_fs_info *info)
 {
 	struct btrfs_path *path;
@@ -10045,6 +10070,19 @@ int btrfs_read_block_groups(struct btrfs_fs_info *info)
 		leaf = path->nodes[0];
 		btrfs_item_key_to_cpu(leaf, &found_key, path->slots[0]);
 
+		/*
+		 * Since block group and chunks are 1:1 mapped and are core
+		 * infrastructure of btrfs, we need to do extra verification.
+		 */
+		ret = verify_chunk_block_group_mapping(info,
+					found_key.objectid, found_key.offset);
+		if (ret < 0) {
+			btrfs_err_rl(info,
+		"block group start=%llu len=%llu doesn't have matched chunk",
+				     found_key.objectid, found_key.offset);
+			goto error;
+		}
+
 		cache = btrfs_create_block_group_cache(info, found_key.objectid,
 						       found_key.offset);
 		if (!cache) {
Signature · 1 line
2.18.0
#1 lore raw
Quoted 56 lines · Qu Wenruo

Reported in https://bugzilla.kernel.org/show_bug.cgi?id=199837, if a crafted btrfs with incorrect chunk<->block group mapping, it could leads to a lot of unexpected behavior.

Although the crafted image can be catched by block group item checker added in "[PATCH] btrfs: tree-checker: Verify block_group_item", if one crafted a valid enough block group item which can pass above check but still mismatch with existing chunk, it could cause a lot of undefined behavior.

This patch will add extra chunk<->block group mapping check at mount time, so such problem can be detected early and cause no harm.

---
 fs/btrfs/extent-tree.c | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)
fs/btrfs/extent-tree.c +25 -0
index 3d9fe58c0080..7a11dc76cd6d 100644
@@ -10003,6 +10003,31 @@ btrfs_create_block_group_cache(struct btrfs_fs_info *fs_info,
 	return cache;
 }
 
+static int verify_chunk_block_group_mapping(struct btrfs_fs_info *fs_info,
+					    u64 start, u64 len)
+{
+	struct btrfs_mapping_tree *map_tree = &fs_info->mapping_tree;
+	struct extent_map *em;
+	int ret;
+
+	read_lock(&map_tree->map_tree.lock);
+	em = lookup_extent_mapping(&map_tree->map_tree, start, len);
+	read_unlock(&map_tree->map_tree.lock);
+
+	if (!em) {
+		ret = -ENOENT;
+		goto out;
+	}
+	if (em->start != start || em->len != len) {
+		ret = -ENOENT;
+		goto out;
+	}
+	ret = 0;
+out:
+	free_extent_map(em);
+	return ret;
+}
+
 int btrfs_read_block_groups(struct btrfs_fs_info *info)
 {
 	struct btrfs_path *path;

fs/btrfs/extent-tree.c int btrfs_read_block_groups(struct btrfs_fs_info *info) · line 10076

Quoted 7 lines
fs/btrfs/extent-tree.c +4 -0
@@ -10045,6 +10070,19 @@ int btrfs_read_block_groups(struct btrfs_fs_info *info)
 		leaf = path->nodes[0];
 		btrfs_item_key_to_cpu(leaf, &found_key, path->slots[0]);
 
+		/*
+		 * Since block group and chunks are 1:1 mapped and are core
+		 * infrastructure of btrfs, we need to do extra verification.
+		 */

nit: I'd rephrase that to just document the invariant that bg and chunks must have 1:1 mapping.

Quoted 13 lines
fs/btrfs/extent-tree.c +9 -0
+		ret = verify_chunk_block_group_mapping(info,
+					found_key.objectid, found_key.offset);
+		if (ret < 0) {
+			btrfs_err_rl(info,
+		"block group start=%llu len=%llu doesn't have matched chunk",
+				     found_key.objectid, found_key.offset);
+			goto error;
+		}
+
 		cache = btrfs_create_block_group_cache(info, found_key.objectid,
 						       found_key.offset);
 		if (!cache) {