Re: [PATCH v5 0/9] xfs: pNFS block layout fixes

From: Carlos Maiolino

Date: Tue Nov 03 2026 - 05:10:19 EST


On Thu, 29 Oct 2026 11:22:57 +0900, Daejun Park wrote:
> The XFS side of the pNFS block and SCSI layout fixes. A pNFS client
> alone can trigger the bugs fixed by patches 1 and 3 to 6. Patch 7
> closes a race with a local process writing to a shared mapping.
> Patches 8 and 9 make a LAYOUTCOMMIT stable the way fdatasync does.
>
> Patch 3 needs patch 2. Patch 4 should not go without patches 2 and 3,
> and patch 6 not without patch 5. Patches 1 to 6 are marked for stable.
> XFS_BMAPI_CONVERT_ONLY takes bit 12 of the bmapi flags, which the
> fs-verity series [1] also uses.
>
> [...]

Applied to for-next, thanks!

[1/9] xfs: mark the inode preallocated for pNFS write layouts past EOF
commit: 77d5d75d727ab3d4c540632ead457d47d3456cd3
[2/9] xfs: add a flag to convert unwritten extents without allocating blocks
commit: e0fbfbec7d5ba059fcb1529054b5447cbe9c6e0e
[3/9] xfs: refuse a pNFS LAYOUTCOMMIT of a range without blocks
commit: faf5f20d6c005af531de079a5a0ea658b305954a
[4/9] xfs: clamp a pNFS LAYOUTCOMMIT extent before computing its end
commit: 351fccff2881e40f4f449bf100aceb47a54688e9
[5/9] xfs: cap the block count of xfs_iomap_write_direct() at one extent
commit: cefa7c7b065d129fe95a64b24ee68ca8c47629c6
[6/9] xfs: clamp the pNFS layout range to the maximum file size
commit: e4211f8034ce04a6bb1e12fc6a054e08b933e5cd
[7/9] xfs: take the invalidate lock while mapping a pNFS layout
commit: d58a23e183d578aca38d7186c353702facbf722b
[8/9] xfs: add datasync and log_flushed arguments to xfs_log_force_inode()
commit: c92cc6514b9c11dd29b90b0a814e8ea87b4a4687
[9/9] xfs: make pNFS LAYOUTCOMMIT stable the way fdatasync does
commit: c3b00a553cbb68b0bebed0ca16d2aa0300d07e56

Best regards,
--
Carlos Maiolino <cem@xxxxxxxxxx>