[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240311122255.2637311-1-yi.zhang@huaweicloud.com>
Date: Mon, 11 Mar 2024 20:22:51 +0800
From: Zhang Yi <yi.zhang@...weicloud.com>
To: linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
djwong@...nel.org,
hch@...radead.org,
brauner@...nel.org,
david@...morbit.com,
tytso@....edu,
jack@...e.cz,
yi.zhang@...wei.com,
yi.zhang@...weicloud.com,
chengzhihao1@...wei.com,
yukuai3@...wei.com
Subject: [PATCH 0/4] xfs/iomap: fix non-atomic clone operation and don't update size when zeroing range post eof
From: Zhang Yi <yi.zhang@...wei.com>
This patch series fix a problem of exposing zeroed data on xfs since the
non-atomic clone operation. This problem was found while I was
developing ext4 buffered IO iomap conversion (ext4 is relying on this
fix [1]), the root cause of this problem and the discussion about the
solution please see [2]. After fix the problem, iomap_zero_range()
doesn't need to update i_size so that ext4 can use it to zero partial
block, e.g. truncate eof block [3].
[1] https://lore.kernel.org/linux-ext4/20240127015825.1608160-1-yi.zhang@huaweicloud.com/
[2] https://lore.kernel.org/linux-ext4/9b0040ef-3d9d-6246-4bdd-82b9a8f55fa2@huaweicloud.com/
[3] https://lore.kernel.org/linux-ext4/9c9f1831-a772-299b-072b-1c8116c3fb35@huaweicloud.com/
Thanks,
Yi.
Zhang Yi (4):
xfs: match lock mode in xfs_buffered_write_iomap_begin()
xfs: convert delayed extents to unwritten when zeroing post eof blocks
iomap: don't increase i_size if it's not a write operation
iomap: cleanup iomap_write_iter()
fs/iomap/buffered-io.c | 78 +++++++++++++++++++++---------------------
fs/xfs/xfs_iomap.c | 39 ++++++++++++++++++---
2 files changed, 73 insertions(+), 44 deletions(-)
--
2.39.2
Powered by blists - more mailing lists