On Tue, 08 Oct 2024 10:59:11 +0200, Christoph Hellwig wrote:
> this is another fallout from the zoned XFS work, which stresses the XFS
> COW I/O path very heavily. It affects normal I/O to reflinked files as
> well, but is very hard to hit there.
>
> The main problem here is that we only punch out delalloc reservations
> from the data fork, but COW I/O places delalloc extents into the COW
> fork, which means that it won't get punched out forshort writes.
>
> [...]
Applied to for-next, thanks!
[01/10] iomap: factor out a iomap_last_written_block helper
commit: c0adf8c3a9bf33f1dd1bf950601380f46a3fcec3
[02/10] iomap: remove iomap_file_buffered_write_punch_delalloc
commit: caf0ea451d97c33c5bbaa0074dad33b0b2a4e649
[03/10] iomap: move locking out of iomap_write_delalloc_release
commit: b78495166264fee1ed7ac44627e1dd080bbdf283
[04/10] xfs: factor out a xfs_file_write_zero_eof helper
commit: 3c399374af28b158854701da324a7bff576f5a97
[05/10] xfs: take XFS_MMAPLOCK_EXCL xfs_file_write_zero_eof
commit: acfbac776496f2093e9facf7876b4015ef8c3d1d
[06/10] xfs: IOMAP_ZERO and IOMAP_UNSHARE already hold invalidate_lock
commit: abd7d651ad2cd2ab1b8cd4dd31e80a8255196db3
[07/10] xfs: support the COW fork in xfs_bmap_punch_delalloc_range
commit: 8fe3b21efa075f29d64a34000e84f89cfaa6cd80
[08/10] xfs: share more code in xfs_buffered_write_iomap_begin
commit: c29440ff66d6f24be5e9e313c1c0eca7212faf9e
[09/10] xfs: set IOMAP_F_SHARED for all COW fork allocations
commit: 7d6fe5c586e6a866f9e69a5bdd72a72b977bab8e
[10/10] xfs: punch delalloc extents from the COW fork for COW writes
commit: f6f91d290c8b9da6e671bd15f306ad2d0e635a04
Best regards,
--
Carlos Maiolino <cem@xxxxxxxxxx>
