diff options
| author | Christian Brauner <brauner@kernel.org> | 2024-08-28 16:54:05 +0200 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2024-08-28 16:54:05 +0200 |
| commit | 7fbabbb4ae2a7203861e4db363e3c861a4df260e (patch) | |
| tree | 4239ed2c4f7f0933e6d9f3a7fc0c86481a8c56a0 /net | |
| parent | 47ac09b91befbb6a235ab620c32af719f8208399 (diff) | |
| parent | 4acaddf5d1e78814d26df3ff02d5e410d951ff32 (diff) | |
Merge patch series "Subject: sort out the fallocate mode mess"
Christoph Hellwig <hch@lst.de> says:
I've recently been looking at the XFS fallocate implementation and got
upset about the messing parsing of the mode argument, which mixes modes
and an optional flag in a really confusing way.
This series tries to clean this up by better defining what is the
operation mode and what is an optional flag, so that both the core
code and file systems can use switch statements to switch on the mode.
* patches from https://lore.kernel.org/r/20240827065123.1762168-1-hch@lst.de:
xfs: refactor xfs_file_fallocate
xfs: move the xfs_is_always_cow_inode check into xfs_alloc_file_space
xfs: call xfs_flush_unmap_range from xfs_free_file_space
fs: sort out the fallocate mode vs flag mess
ext4: remove tracing for FALLOC_FL_NO_HIDE_STALE
block: remove checks for FALLOC_FL_NO_HIDE_STALE
Link: https://lore.kernel.org/r/20240827065123.1762168-1-hch@lst.de
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions