diff options
| author | Nikolay Borisov <nborisov@suse.com> | 2020-10-01 09:40:39 +0300 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2020-10-07 12:18:00 +0200 |
| commit | 1fd4033dd011a3525bacddf37ab9eac425d25c4f (patch) | |
| tree | 318d374d3048ca15547b26018fea7ff86263515a /include/trace | |
| parent | 8d1a7aae89dc0c41ffb76fe1007dbba59d13881b (diff) | |
btrfs: rename BTRFS_INODE_ORDERED_DATA_CLOSE flag
Commit 8d875f95da43 ("btrfs: disable strict file flushes for
renames and truncates") eliminated the notion of ordered operations and
instead BTRFS_INODE_ORDERED_DATA_CLOSE only remained as a flag
indicating that a file's content should be synced to disk in case a
file is truncated and any writes happen to it concurrently. In fact
this intendend behavior was broken until it was fixed in
f6dc45c7a93a ("Btrfs: fix filemap_flush call in btrfs_file_release").
All things considered let's give the flag a more descriptive name. Also
slightly reword comments.
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'include/trace')
0 files changed, 0 insertions, 0 deletions