diff options
| author | David Sterba <dsterba@suse.com> | 2020-06-09 19:56:06 +0200 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2020-06-14 01:19:02 +0200 |
| commit | 55e20bd12a56e06c38b953177bb162cbbaa96004 (patch) | |
| tree | b19873031657b8f2c5870cfbc683c67c29547733 /fs/btrfs/Kconfig | |
| parent | f1084bc60a1ec592011a805a0f925f2f1205897d (diff) | |
| download | lwn-55e20bd12a56e06c38b953177bb162cbbaa96004.tar.gz lwn-55e20bd12a56e06c38b953177bb162cbbaa96004.zip | |
Revert "btrfs: switch to iomap_dio_rw() for dio"
This reverts commit a43a67a2d715540c1368b9501a22b0373b5874c0.
This patch reverts the main part of switching direct io implementation
to iomap infrastructure. There's a problem in invalidate page that
couldn't be solved as regression in this development cycle.
The problem occurs when buffered and direct io are mixed, and the ranges
overlap. Although this is not recommended, filesystems implement
measures or fallbacks to make it somehow work. In this case, fallback to
buffered IO would be an option for btrfs (this already happens when
direct io is done on compressed data), but the change would be needed in
the iomap code, bringing new semantics to other filesystems.
Another problem arises when again the buffered and direct ios are mixed,
invalidation fails, then -EIO is set on the mapping and fsync will fail,
though there's no real error.
There have been discussions how to fix that, but revert seems to be the
least intrusive option.
Link: https://lore.kernel.org/linux-btrfs/20200528192103.xm45qoxqmkw7i5yl@fiona/
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/Kconfig')
| -rw-r--r-- | fs/btrfs/Kconfig | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/fs/btrfs/Kconfig b/fs/btrfs/Kconfig index 68b95ad82126..575636f6491e 100644 --- a/fs/btrfs/Kconfig +++ b/fs/btrfs/Kconfig @@ -14,7 +14,6 @@ config BTRFS_FS select LZO_DECOMPRESS select ZSTD_COMPRESS select ZSTD_DECOMPRESS - select FS_IOMAP select RAID6_PQ select XOR_BLOCKS select SRCU |