summaryrefslogtreecommitdiffstats
path: root/fs/fhandle.c
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@gmail.com>2014-05-25 04:55:44 +0200
committerChris Mason <clm@fb.com>2014-06-10 02:21:03 +0200
commitc55bfa67e94e22ec0449fe7c55b3ef20fbe13348 (patch)
tree5c56b113d932a22ef584926f7ef9429baa9f3396 /fs/fhandle.c
parentBtrfs: ensure readers see new data after a clone operation (diff)
downloadlinux-c55bfa67e94e22ec0449fe7c55b3ef20fbe13348.tar.xz
linux-c55bfa67e94e22ec0449fe7c55b3ef20fbe13348.zip
Btrfs: set dead flag on the right root when destroying snapshot
We were setting the BTRFS_ROOT_SUBVOL_DEAD flag on the root of the parent of our target snapshot, instead of setting it in the target snapshot's root. This is easy to observe by running the following scenario: mkfs.btrfs -f /dev/sdd mount /dev/sdd /mnt btrfs subvolume create /mnt/first_subvol btrfs subvolume snapshot -r /mnt /mnt/mysnap1 btrfs subvolume delete /mnt/first_subvol btrfs subvolume snapshot -r /mnt /mnt/mysnap2 btrfs send -p /mnt/mysnap1 /mnt/mysnap2 -f /tmp/send.data The send command failed because the send ioctl returned -EPERM. A test case for xfstests follows. Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com> Reviewed-by: David Sterba <dsterba@suse.cz> Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'fs/fhandle.c')
0 files changed, 0 insertions, 0 deletions