kernel.git/fs/btrfs/send.h, branch linux-6.3.y

btrfs: send add define for v2 buffer size

2022-12-05T17:00:41Z

Add a define for the data buffer size (though the maximum size is not limited by it) BTRFS_SEND_BUF_SIZE_V2 so it's more visible. Signed-off-by: Wang Yugui Reviewed-by: David Sterba Signed-off-by: David Sterba

btrfs: send: allow protocol version 3 with CONFIG_BTRFS_DEBUG

2022-10-11T12:46:55Z

We haven't finalized send stream v3 yet, so gate the send stream version behind CONFIG_BTRFS_DEBUG as we want some way to test it. The original verity send did not check the protocol version, so add that actual protection as well. Reviewed-by: Anand Jain Signed-off-by: Boris Burkov Signed-off-by: David Sterba

btrfs: send: add support for fs-verity

2022-09-26T10:27:55Z

Preserve the fs-verity status of a btrfs file across send/recv. There is no facility for installing the Merkle tree contents directly on the receiving filesystem, so we package up the parameters used to enable verity found in the verity descriptor. This gives the receive side enough information to properly enable verity again. Note that this means that receive will have to re-compute the whole Merkle tree, similar to how compression worked before encoded_write. Since the file becomes read-only after verity is enabled, it is important that verity is added to the send stream after any file writes. Therefore, when we process a verity item, merely note that it happened, then actually create the command in the send stream during 'finish_inode_if_needed'. This also creates V3 of the send stream format, without any format changes besides adding the new commands and attributes. Signed-off-by: Boris Burkov Signed-off-by: David Sterba

btrfs: send: add new command FILEATTR for file attributes

2022-07-25T15:45:38Z

There are file attributes inherited from previous ext2 SETFLAGS/GETFLAGS and later from XFLAGS interfaces, now commonly found under the 'fileattr' API. This corresponds to the individual inode bits and that's part of the on-disk format, so this is suitable for the protocol. The other interfaces contain a lot of cruft or bits that btrfs does not support yet. Currently the value is u64 and matches btrfs_inode_item. Not all the bits can be set by ioctls (like NODATASUM or READONLY), but we can send them over the protocol and leave it up to the receiving side what and how to apply. As some of the flags, eg. IMMUTABLE, can prevent any further changes, the receiving side needs to understand that and apply the changes in the right order, or possibly with some intermediate steps. This should be easier, future proof and simpler on the protocol layer than implementing in kernel. Reviewed-by: Omar Sandoval Signed-off-by: David Sterba

btrfs: send: simplify includes

2022-07-25T15:45:37Z

We don't need the whole ctree.h in send.h, none of the data types defined there are used. Signed-off-by: David Sterba

btrfs: send: drop KERNEL ifdef from send.h

2022-07-25T15:45:37Z

We don't need this ifdef as the header file is not shared, the protocol definition used by userspace should be from libbtrfs or libbtrfsutil. Signed-off-by: David Sterba

btrfs: send: enable support for stream v2 and compressed writes

2022-07-25T15:45:32Z

Now that the new support is implemented, allow the ioctl to accept v2 and the compressed flag, and update the version in sysfs. Signed-off-by: Omar Sandoval Signed-off-by: David Sterba

btrfs: send: add stream v2 definitions

2022-07-25T15:45:32Z

This adds the definitions of the new commands for send stream version 2 and their respective attributes: fallocate, FS_IOC_SETFLAGS (a.k.a. chattr), and encoded writes. It also documents two changes to the send stream format in v2: the receiver shouldn't assume a maximum command size, and the DATA attribute is encoded differently to allow for writes larger than 64k. These will be implemented in subsequent changes, and then the ioctl will accept the new version and flag. Reviewed-by: Josef Bacik Signed-off-by: Omar Sandoval Signed-off-by: David Sterba

btrfs: send: explicitly number commands and attributes

2022-07-25T15:45:32Z

Commit e77fbf990316 ("btrfs: send: prepare for v2 protocol") added _BTRFS_SEND_C_MAX_V* macros equal to the maximum command number for the version plus 1, but as written this creates gaps in the number space. The maximum command number is currently 22, and __BTRFS_SEND_C_MAX_V1 is accordingly 23. But then __BTRFS_SEND_C_MAX_V2 is 24, suggesting that v2 has a command numbered 23, and __BTRFS_SEND_C_MAX is 25, suggesting that 23 and 24 are valid commands. Instead, let's explicitly number all of the commands, attributes, and sentinel MAX constants. Signed-off-by: Omar Sandoval Reviewed-by: David Sterba Signed-off-by: David Sterba

btrfs: reuse existing inode from btrfs_ioctl

2022-03-14T12:13:46Z

btrfs_ioctl extracts inode from file so we can pass that into the callbacks. Signed-off-by: Sahil Kang Reviewed-by: David Sterba Signed-off-by: David Sterba

kernel.git/fs/btrfs/send.h, branch linux-6.3.y

btrfs: send add define for v2 buffer size

btrfs: send: allow protocol version 3 with CONFIG_BTRFS_DEBUG

btrfs: send: add support for fs-verity

btrfs: send: add new command FILEATTR for file attributes

btrfs: send: simplify includes

btrfs: send: drop __KERNEL__ ifdef from send.h

btrfs: send: enable support for stream v2 and compressed writes

btrfs: send: add stream v2 definitions

btrfs: send: explicitly number commands and attributes

btrfs: reuse existing inode from btrfs_ioctl

btrfs: send: drop KERNEL ifdef from send.h