Re: [PATCH -next v6 0/2] iomap/xfs: fix stale data exposure when truncating realtime inodes

[Christian Brauner <brauner@kernel.org>]

On Tue, 18 Jun 2024 22:21:10 +0800, Zhang Yi wrote:
> Changes since v5:
>  - Drop all the code about zeroing out the whole allocation unitsize
>    on truncate down in xfs_setattr_size() as Christoph suggested, let's
>    just fix this issue for RT file by converting tail blocks to
>    unwritten now, and we could think about forced aligned extent and
>    atomic write later until it needs, so only pick patch 6 and 8 in
>    previous version, do some minor git log changes.
> 
> [...]

I've put this into vfs.iomap for testing which should end up in fs-next asap.

---

Applied to the vfs.iomap branch of the vfs/vfs.git tree.
Patches in the vfs.iomap 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.iomap

[1/2] xfs: reserve blocks for truncating large realtime inode
      https://git.kernel.org/vfs/vfs/c/d048945150b7
[2/2] iomap: don't increase i_size in iomap_write_end()
      https://git.kernel.org/vfs/vfs/c/602f09f4029c