On Mon, Jul 02, 2018 at 11:29:12AM -0600, Ross Zwisler wrote:
Follow the lead of xfs_break_dax_layouts() and add synchronization
operations in ext4 which remove blocks from an inode (hole punch, truncate
down, etc.) and pages which are pinned due to DAX DMA operations.
Signed-off-by: Ross Zwisler <ross.zwisler(a)linux.intel.com>
Reviewed-by: Jan Kara <jack(a)suse.cz>
Reviewed-by: Lukas Czerner <lczerner(a)redhat.com>
Changes since v2:
* Added a comment to ext4_insert_range() explaining why we don't call
Which I think is wrong and will cause data corruption.
@@ -5651,6 +5663,11 @@ int ext4_insert_range(struct inode *inode,
loff_t offset, loff_t len)
+ * We don't need to call ext4_break_layouts() because we aren't
+ * removing any blocks from the inode. We are just changing their
+ * offset by inserting a hole.
The entire point of these leases is so that a thrid party can
directly access the blocks underlying the file. That means they are
keeping their own file offset<->disk block mapping internally, and
they are assuming that it is valid for as long as they hold the
lease. If the filesystem modifies the extent map - even something
like a shift here which changes the offset<->disk block mapping -
the userspace app now has a stale mapping and so the lease *must be
broken* to tell it that it's mappings are now stale and it needs to
If the app doesn't refetch it's mappings after something like a
shift, it will be reading and writing data from the wrong file
offset, and that will lead to the app silently corrupting it's data.
IOWs, layouts need to be broken by any operation that modifies the
extent map in any way, not just those operations that remove blocks.