mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2026-05-13 09:28:44 -04:00
btrfs: fix the ram_bytes assignment for truncated ordered extents
[HICCUP] After adding extra checks on btrfs_file_extent_item::ram_bytes to tree-checker, running fsstress leads to tree-checker warning at write time, as we created file extent items with an invalid ram_bytes. All those offending file extents have offset 0, and ram_bytes matching num_bytes, and smaller than disk_num_bytes. This would also trigger the recently enhanced btrfs-check, which catches such mismatches and report them as minor errors. [CAUSE] When a folio/page is invalidated and it is part of a submitted OE, we mark the OE truncated just to the beginning of the folio/page. And for truncated OE, we insert the file extent item with incorrect value for ram_bytes (using num_bytes instead of the usual value). This is not a big deal for end users, as we do not utilize the ram_bytes field for regular non-compressed extents. This mismatch is just a small violation against on-disk format. [FIX] Fix it by removing the override on btrfs_file_extent_item::ram_bytes. Reviewed-by: Filipe Manana <fdmanana@suse.com> Signed-off-by: Qu Wenruo <wqu@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
@@ -2960,10 +2960,8 @@ static int insert_ordered_extent_file_extent(struct btrfs_trans_handle *trans,
|
||||
btrfs_set_stack_file_extent_disk_num_bytes(&stack_fi,
|
||||
oe->disk_num_bytes);
|
||||
btrfs_set_stack_file_extent_offset(&stack_fi, oe->offset);
|
||||
if (test_bit(BTRFS_ORDERED_TRUNCATED, &oe->flags)) {
|
||||
if (test_bit(BTRFS_ORDERED_TRUNCATED, &oe->flags))
|
||||
num_bytes = oe->truncated_len;
|
||||
ram_bytes = num_bytes;
|
||||
}
|
||||
btrfs_set_stack_file_extent_num_bytes(&stack_fi, num_bytes);
|
||||
btrfs_set_stack_file_extent_ram_bytes(&stack_fi, ram_bytes);
|
||||
btrfs_set_stack_file_extent_compression(&stack_fi, oe->compress_type);
|
||||
|
||||
Reference in New Issue
Block a user