mbox series

[0/3] iomap/xfs: fix stale data exposure when truncating realtime inodes

Message ID 20240515022829.2455554-1-yi.zhang@huaweicloud.com (mailing list archive)
Headers show
Series iomap/xfs: fix stale data exposure when truncating realtime inodes | expand

Message

Zhang Yi May 15, 2024, 2:28 a.m. UTC 
From: Zhang Yi <yi.zhang@huawei.com>

This series fix a stale data exposure issue reported by Chandan when
running fstests generic/561 on xfs with realtime device[1]. The real
problem is xfs_setattr_size() doesn't zero out enough range when
truncating a realtime inode, please see the third patch or [1] for
details.

The first two patches modify iomap_truncate_page() and
dax_truncate_page() to pass filesystem identified blocksize, and drop
the assumption of i_blocksize() as Dave suggested. The third patch fix
the issue by modifying xfs_truncate_page() to pass the correct
blocksize, and make sure zeroed range have been flushed to disk before
updating i_size.

[1] https://lore.kernel.org/linux-xfs/87ttj8ircu.fsf@debian-BULLSEYE-live-builder-AMD64/

Thanks,
Yi.

Zhang Yi (3):
  iomap: pass blocksize to iomap_truncate_page()
  fsdax: pass blocksize to dax_truncate_page()
  xfs: correct the zeroing truncate range

 fs/dax.c               |  7 +++----
 fs/ext2/inode.c        |  4 ++--
 fs/iomap/buffered-io.c |  7 +++----
 fs/xfs/xfs_iomap.c     | 36 ++++++++++++++++++++++++++++++++----
 fs/xfs/xfs_iops.c      | 10 ----------
 include/linux/dax.h    |  4 ++--
 include/linux/iomap.h  |  4 ++--
 7 files changed, 44 insertions(+), 28 deletions(-)