diff options
| author | Josef Bacik <[email protected]> | 2020-01-17 09:02:19 -0500 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2020-03-23 17:01:24 +0100 |
| commit | 790a1d44f93f465b37d9d4ff22eea1850a079309 (patch) | |
| tree | fc20499f48b27268ebf9a8cde038634b1e0f5262 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | cfe953c8240d1b21a81b8bd7f33cfe0b96b89f38 (diff) | |
btrfs: use btrfs_ordered_update_i_size in clone_finish_inode_update
We were using btrfs_i_size_write(), which unconditionally jacks up
inode->disk_i_size. However since clone can operate on ranges we could
have pending ordered extents for a range prior to the start of our clone
operation and thus increase disk_i_size too far and have a hole with no
file extent.
Fix this by using the btrfs_ordered_update_i_size helper which will do
the right thing in the face of pending ordered extents outside of our
clone range.
Reviewed-by: Filipe Manana <[email protected]>
Signed-off-by: Josef Bacik <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions