Re: [PATCH v2 0/2] exfat: fix iomap mapping vs truncate race

From: Namjae Jeon

Date: Tue Nov 17 2026 - 06:07:07 EST


On Mon, Nov 16, 2026 at 6:07 PM Youling Tang <youling.tang@xxxxxxxxx> wrote:
>
> From: Youling Tang <tangyouling@xxxxxxxxxx>
>
> This series fixes two related problems in the exfat iomap path.
>
> Patch 1 fixes a race between iomap mapping and truncate: i_size was read
> twice, and a shrink in between could make the mapping length negative,
> which underflowed the cluster count.
>
> Patch 2 fixes the handling of the EXFAT_EOF_CLUSTER sentinel. The iomap
> code used to convert it into a physical address; now exfat_map_cluster()
> maps only the valid prefix when a range straddles the end of the chain,
> and iomap reports the remaining range as a hole, matching the old
> buffer_head code.
>
> Patch 2 relies on the non-negative length guaranteed by patch 1 for the
> hole mapping.
>
> Changes since v1:
> - Move the valid-prefix clamp into exfat_map_cluster().
>
> v1: https://lore.kernel.org/exfat/20261113080658.2440516-1-youling.tang@xxxxxxxxx/T/#t
>
> Youling Tang (2):
> exfat: fix iomap mapping when writeback races with truncate
> exfat: don't map EXFAT_EOF_CLUSTER as a physical cluster
Applied them to #dev.
Thanks!