Re: (subset) [PATCH v4 0/5] exfat: fix valid_size update races
From: Christian Brauner
Date: Tue Nov 17 2026 - 12:16:55 EST
On Mon, 16 Nov 2026 16:57:47 +0800, Chi Zhiling wrote:
> From: Chi Zhiling <chizhiling@xxxxxxxxxx>
>
> exFAT uses valid_size (ValidDataLength) as the on-disk boundary of
> initialised data, but the current code advances it too late and without
> proper serialisation. Buffered writes can silently lose data reclaimed
> before valid_size covers it, file expansion and page faults can
> initialise the same range concurrently, and a failed or short direct
> write can still grow the file on disk.
>
> [...]
Applied to the vfs-7.5.iomap branch of the vfs/vfs.git tree.
Patches in the vfs-7.5.iomap branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-7.5.iomap
[1/5] iomap: export iomap_bio_read_folio_range_sync()
https://git.kernel.org/vfs/vfs/c/4c7bbc7f82ff