| Message ID | 20241209114241.3725722-1-leo.lilong@huawei.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | iomap: fix zero padding data issue in concurrent append writes | expand |
On Mon, 09 Dec 2024 19:42:38 +0800, Long Li wrote: > This patch series fixes zero padding data issues in concurrent append write > scenarios. A detailed problem description and solution can be found in patch 2. > Patch 1 is introduced as preparation for the fix in patch 2, eliminating the > need to resample inode size for io_size trimming and avoiding issues caused > by inode size changes during concurrent writeback and truncate operations. > Patch 3 is a minor cleanup. > > [...] Applied to the vfs.fixes branch of the vfs/vfs.git tree. Patches in the vfs.fixes 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.fixes [1/3] iomap: pass byte granular end position to iomap_add_to_ioend https://git.kernel.org/vfs/vfs/c/f307c58239b5 [2/3] iomap: fix zero padding data issue in concurrent append writes https://git.kernel.org/vfs/vfs/c/33e72d56fb3a [3/3] xfs: clean up xfs_end_ioend() to reuse local variables https://git.kernel.org/vfs/vfs/c/30e611890d89
Can you please drop the third patch? We'll probably have something in XFS that will conflict with it if not reabsed, so it's probably better to merge it through the xfs tree so that everything can be properly merged.
On Mon, 09 Dec 2024 19:42:38 +0800, Long Li wrote: > This patch series fixes zero padding data issues in concurrent append write > scenarios. A detailed problem description and solution can be found in patch 2. > Patch 1 is introduced as preparation for the fix in patch 2, eliminating the > need to resample inode size for io_size trimming and avoiding issues caused > by inode size changes during concurrent writeback and truncate operations. > Patch 3 is a minor cleanup. > > [...] Applied to the vfs.fixes branch of the vfs/vfs.git tree. Patches in the vfs.fixes 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.fixes [1/3] iomap: pass byte granular end position to iomap_add_to_ioend https://git.kernel.org/vfs/vfs/c/b44679c63e4d [2/3] iomap: fix zero padding data issue in concurrent append writes https://git.kernel.org/vfs/vfs/c/51d20d1dacbe
On Tue, Dec 10, 2024 at 03:38:48AM -0800, Christoph Hellwig wrote: > Can you please drop the third patch? We'll probably have something in > XFS that will conflict with it if not reabsed, so it's probably better > to merge it through the xfs tree so that everything can be properly > merged. Done.