We have a BUG_ON() in read_fs_root that expects key->offset == (u64)-1. Restore
will just pass in the location it reads out of the inode if it has a subvol
reference and pass that in, which doesn't have offset == (u64)-1, so it causes
restore blow up. This was reported in bugzilla and this patch fixed the
problem. Thanks,
Signed-off-by: Josef Bacik <jbacik@xxxxxxxxxxxx>
---
cmds-restore.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/cmds-restore.c b/cmds-restore.c
index 12b2188..aada7d0 100644
--- a/cmds-restore.c
+++ b/cmds-restore.c
@@ -612,6 +612,7 @@ static int search_dir(struct btrfs_root *root, struct btrfs_key *key,
goto next;
}
+ location.offset = (u64)-1;
search_root = btrfs_read_fs_root(root->fs_info,
&location);
if (IS_ERR(search_root)) {
--
1.7.7.6
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
