Displaying 2 results from an estimated 2 matches for "btrfs_send_c_max".
2013 Jan 07
3
[PATCH] btrfs: add "no file data" flag to btrfs send ioctl
..._send_args {
__s64 send_fd; /* in */
__u64 clone_sources_count; /* in */
diff --git a/fs/btrfs/send.c b/fs/btrfs/send.c
index e78b297..d725536 100644
--- a/fs/btrfs/send.c
+++ b/fs/btrfs/send.c
@@ -85,6 +85,7 @@ struct send_ctx {
u32 send_max_size;
u64 total_send_size;
u64 cmd_send_size[BTRFS_SEND_C_MAX + 1];
+ u64 flags; /* ''flags'' member of btrfs_ioctl_send_args is u64 */
struct vfsmount *mnt;
@@ -3707,6 +3708,39 @@ out:
return ret;
}
+/*
+ * Send an update extent command to user space.
+ */
+static int send_update_extent(struct send_ctx *sctx,
+ u64 offset,...
2013 Dec 16
6
[PATCH 0/3] Send: minor cleanups, add RO checks
First two patches are trivial cleanups that I''ve spotted while reading send.c,
can be applied independently.
The third patch contains the important bits, safety checks that the subvolumes
involved in send do not accidentally lose the RO status. I haven''t seen this
documented anywhere that this is mandatory, implied from how I assume send
works. Please let me know if this is