Normally when specifying max_inline, we should normally limit it by uncompressed extent size, as it's the only thing user can control. (Control the algorithm and compressed data is almost impossible)
Since btrfs is providing *TRANSPARENT* compression, max_inline should behave the same for both plain and compress data. So this patch will use @inline_len instead of @data_len in cow_file_range_inline() so user will know their max_inline mount option works exactly the same for both plain and compressed data extent. Signed-off-by: Qu Wenruo <w...@suse.com> --- fs/btrfs/inode.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index e1a7f3cb5be9..48472509239b 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -303,7 +303,7 @@ static noinline int cow_file_range_inline(struct btrfs_root *root, (!compressed_size && (actual_end & (fs_info->sectorsize - 1)) == 0) || end + 1 < isize || - data_len > fs_info->max_inline) { + inline_len > fs_info->max_inline) { return 1; } -- 2.16.2 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html