diff options
| author | Yan Zheng <zheng.yan@oracle.com> | 2009-01-06 14:58:02 (GMT) |
|---|---|---|
| committer | Chris Mason <chris.mason@oracle.com> | 2009-01-06 14:58:02 (GMT) |
| commit | 1ba12553f3600ffebad226c5204ab0e46df98161 (patch) | |
| tree | 081d39d935782a34d4726a55f608de3237b57d9d /fs/btrfs | |
| parent | 180591bcfed1a2cec048abb21d3dab840625caab (diff) | |
| download | linux-1ba12553f3600ffebad226c5204ab0e46df98161.tar.xz | |
Btrfs: don't change file extent's ram_bytes in btrfs_drop_extents
btrfs_drop_extents doesn't change file extent's ram_bytes
in the case of booked extent. To be consistent, we should
also not change ram_bytes when truncating existing extent.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Diffstat (limited to 'fs/btrfs')
| -rw-r--r-- | fs/btrfs/file.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c index 0e3a13a..9026833 100644 --- a/fs/btrfs/file.c +++ b/fs/btrfs/file.c @@ -556,10 +556,6 @@ next_slot: inode_sub_bytes(inode, old_num - new_num); } - if (!compression && !encryption) { - btrfs_set_file_extent_ram_bytes(leaf, - extent, new_num); - } btrfs_set_file_extent_num_bytes(leaf, extent, new_num); btrfs_mark_buffer_dirty(leaf); |