Files
linux/fs
Christoph Hellwig 8d3c1fa3fa f2fs: don't rely on F2FS_MAP_* in f2fs_iomap_begin
When testing with a mixed zoned / convention device combination, there
are regular but not 100% reproducible failures in xfstests generic/113
where the __is_valid_data_blkaddr assert hits due to finding a hole.

This seems to be because f2fs_map_blocks can set this flag on a hole
when it was found in the extent cache.

Rework f2fs_iomap_begin to just check the special block numbers directly.
This has the added benefits of the WARN_ON showing which invalid block
address we found, and being properly error out on delalloc blocks that
are confusingly called unwritten but not actually suitable for direct
I/O.

Fixes: 1517c1a7a4 ("f2fs: implement iomap operations")
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Chao Yu <chao@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
2023-01-06 15:12:28 -08:00
..
2022-12-22 11:40:35 +00:00
2022-12-11 18:12:18 -08:00
2022-10-20 10:13:27 +02:00
2022-09-24 07:00:00 +02:00
2022-12-11 18:12:18 -08:00
2022-05-09 16:21:46 -04:00
2022-09-11 20:26:07 -07:00
2022-11-25 17:01:22 +09:00
2022-10-20 10:13:27 +02:00
2022-08-20 11:34:33 -04:00
2022-12-11 18:12:17 -08:00
2022-12-21 14:45:25 +01:00
2022-06-28 13:58:05 -04:00
2022-10-26 10:02:34 +02:00