mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-03 17:40:04 +00:00
Btrfs: fix EIO from btrfs send in is_extent_unchanged for punched holes
When you take a snapshot, punch a hole where there has been data, then take another snapshot and try to send an incremental stream, btrfs send would give you EIO. That is because is_extent_unchanged had no support for holes being punched. With this patch, instead of returning EIO we just return 0 (== the extent is not unchanged) and we're good. Signed-off-by: Jan Schmidt <list.btrfs@jan-o-sch.net> Cc: Alexander Block <ablock84@gmail.com> Signed-off-by: Josef Bacik <jbacik@fusionio.com>
This commit is contained in:
parent
4adaa61102
commit
adaa4b8e4d
1 changed files with 4 additions and 6 deletions
|
@ -3945,12 +3945,10 @@ static int is_extent_unchanged(struct send_ctx *sctx,
|
|||
found_key.type != key.type) {
|
||||
key.offset += right_len;
|
||||
break;
|
||||
} else {
|
||||
if (found_key.offset != key.offset + right_len) {
|
||||
/* Should really not happen */
|
||||
ret = -EIO;
|
||||
goto out;
|
||||
}
|
||||
}
|
||||
if (found_key.offset != key.offset + right_len) {
|
||||
ret = 0;
|
||||
goto out;
|
||||
}
|
||||
key = found_key;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue