Patch "xfs: cap the block count of xfs_iomap_write_direct() at one extent" has been added to the 7.3-stable tree
Sasha Levin
AppliedThis is a note to let you know that I've just added the patch titled
xfs: cap the block count of xfs_iomap_write_direct() at one extent
to the 7.3-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
xfs-cap-the-block-count-of-xfs_iomap_write_direct-at.patch
and it can be found in the queue-7.3 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
commit cf3aa748f2b5d10031c673cfec5f0d4e850a56c2
Author: Daejun Park <[email protected]> Date: Thu Oct 29 11:23:02 2026 +0900
xfs: cap the block count of xfs_iomap_write_direct() at one extent
[ Upstream commit 66d1ce09ebd72709f8d739630c39f440445173fd ]
xfs_iomap_write_direct() reserves blocks for the whole count in an unsigned int. For a pNFS layout the client chooses that count, and an RW LAYOUTGET for 16 TiB wraps the reservation and shuts XFS down.
xfs_bmapi_write() maps at most XFS_MAX_BMBT_EXTLEN blocks here, so cap the count at that. nfsd asks again for the rest. The other callers get the same mapping as before.
fs/xfs/xfs_iomap.c +8 -0
@@ -285,6 +285,14 @@ xfs_iomap_write_direct(ASSERT (count_fsb >0 ); +/* +* xfs_bmapi_write() maps at most XFS_MAX_BMBT_EXTLEN blocks in one +* mapping, so don't reserve blocks for more. A pNFS layout range +* comes from a client, and its block count may not even fit the +* 32-bit reservation. The caller maps the rest with a later call. +*/ + count_fsb =min_t (xfs_filblks_t, count_fsb,XFS_MAX_BMBT_EXTLEN ); + resaligned =xfs_aligned_fsb_count (offset_fsb, count_fsb,xfs_get_extsz_hint (ip));if (unlikely (XFS_IS_REALTIME_INODE (ip))) {