Changes in iomap.c

03a43677ca91e3997355a13b1da6e47329b025e1 - exfat: add swap_activate support

Tue, 09 Jun 2026 11:21:49 +0200

exfat: add swap_activate supportCommit 07d67f3e9083 ("exfat: add iomap buffered I/O support")converted exfat buffered I/O to iomap, but did not add a.swap_activate handler to the address_space_operations.swapon(2) on an exfat swapfile then fails with EINVAL, which causesLTP swap tests to fail.Add exfat_iomap_swap_activate() and hook it into exfat_aops so exfatuses iomap_swapfile_activate() for swapfile activation.Fixes: 614f71ca1bdf ("exfat: add iomap buffered I/O support")Closes: https://lore.kernel.org/all/20260603110212.3020276-1-japo@linux.ibm.com/Signed-off-by: Jan Polensky Signed-off-by: Namjae Jeon List of files: /linux/fs/exfat/iomap.c

b4b7fe2c7cbf519ab5e7edc6625c71608805fb1d - exfat: add support for SEEK_HOLE and SEEK_DATA in llseek

Sat, 23 May 2026 06:59:28 +0200

exfat: add support for SEEK_HOLE and SEEK_DATA in llseekAdds exfat_file_llseek() that implements these whence values viathe iomap layer (iomap_seek_hole() and iomap_seek_data()) using theexisting exfat_read_iomap_ops.Unlike many other modern filesystems, exFAT does not support sparse fileswith unallocated clusters (holes). In exFAT, clusters are always fullyallocated once they are written or preallocated. In addition, exFATmaintains a separate "Valid Data Length" (valid_size) that is distinctfrom the logical file size. This affects how holes are reported duringseeking. In exfat_iomap_begin(), ranges where the offset is greaterthan or equal to ei->valid_size are mapped as IOMAP_UNWRITTEN, while rangesbelow valid_size are mapped as IOMAP_MAPPED. This mapping behavior is usedby the iomap seek functions to correctly report SEEK_HOLE and SEEK_DATApositions. - Ranges with offset >= ei->valid_size are mapped as IOMAP_HOLE. - Ranges with offset < ei->valid_size are mapped as IOMAP_MAPPED.Reviewed-by: Christoph Hellwig Acked-by: Christoph Hellwig Acked-by: "Darrick J. Wong" Signed-off-by: Namjae Jeon List of files: /linux/fs/exfat/iomap.c

867b9c96dc837e09ef125a79dc151fa2fc7a5d32 - exfat: add iomap direct I/O support

Sat, 23 May 2026 06:56:43 +0200

exfat: add iomap direct I/O supportAdd iomap-based direct I/O support to the exfat filesystem. This replacesthe previous exfat_direct_IO() implementation that usedblockdev_direct_IO() with iomap_dio_rw() interface.Reviewed-by: Christoph Hellwig Acked-by: Christoph Hellwig Acked-by: "Darrick J. Wong" Signed-off-by: Namjae Jeon List of files: /linux/fs/exfat/iomap.c

82a81a7352bcf5f2756ac33d47ee0582737e9a85 - exfat: add iomap buffered I/O support

Mon, 15 Jun 2026 12:59:58 +0200

exfat: add iomap buffered I/O supportAdd full buffered I/O support using the iomap framework to the exfatfilesystem. This will replaces the old exfat_get_block(),exfat_write_begin(), exfat_write_end(), and exfat_block_truncate_page()with their iomap equivalents. Buffered writes now useiomap_file_buffered_write(), read uses iomap_bio_read_folio() andiomap_bio_readahead(), and writeback is handled through iomap_writepages().Acked-by: Christoph Hellwig Acked-by: "Darrick J. Wong" Signed-off-by: Namjae Jeon List of files: /linux/fs/exfat/iomap.c