Revision adaa4b8e4d47eeb114513c2f7a172929154b94bd authored by Jan Schmidt on 21 March 2013, 14:30:23 UTC, committed by Josef Bacik on 28 March 2013, 13:51:26 UTC
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>
1 parent 4adaa61
| File | Mode | Size |
|---|---|---|
| apparmor | ||
| integrity | ||
| keys | ||
| selinux | ||
| smack | ||
| tomoyo | ||
| yama | ||
| Kconfig | -rw-r--r-- | 5.7 KB |
| Makefile | -rw-r--r-- | 1.0 KB |
| capability.c | -rw-r--r-- | 23.8 KB |
| commoncap.c | -rw-r--r-- | 28.1 KB |
| device_cgroup.c | -rw-r--r-- | 14.8 KB |
| inode.c | -rw-r--r-- | 6.7 KB |
| lsm_audit.c | -rw-r--r-- | 9.3 KB |
| min_addr.c | -rw-r--r-- | 1.3 KB |
| security.c | -rw-r--r-- | 35.1 KB |
Computing file changes ...
