Chao Yu
8acae04721
f2fs: compress: don't allow unaligned truncation on released compress inode
...
[ Upstream commit 29ed2b5dd521ce7c5d8466cd70bf0cc9d07afeee ]
f2fs image may be corrupted after below testcase:
- mkfs.f2fs -O extra_attr,compression -f /dev/vdb
- mount /dev/vdb /mnt/f2fs
- touch /mnt/f2fs/file
- f2fs_io setflags compression /mnt/f2fs/file
- dd if=/dev/zero of=/mnt/f2fs/file bs=4k count=4
- f2fs_io release_cblocks /mnt/f2fs/file
- truncate -s 8192 /mnt/f2fs/file
- umount /mnt/f2fs
- fsck.f2fs /dev/vdb
[ASSERT] (fsck_chk_inode_blk:1256) --> ino: 0x5 has i_blocks: 0x00000002, but has 0x3 blocks
[FSCK] valid_block_count matching with CP [Fail] [0x4, 0x5]
[FSCK] other corrupted bugs [Fail]
The reason is: partial truncation assume compressed inode has reserved
blocks, after partial truncation, valid block count may change w/o
.i_blocks and .total_valid_block_count update, result in corruption.
This patch only allow cluster size aligned truncation on released
compress inode for fixing.
Fixes: c61404153eb6 ("f2fs: introduce FI_COMPRESS_RELEASED instead of using IMMUTABLE bit")
Signed-off-by: Chao Yu <chao@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2024-06-16 13:39:40 +02:00
..
2021-08-18 22:08:24 +02:00
2021-08-18 22:08:24 +02:00
2024-06-16 13:39:36 +02:00
2024-06-16 13:39:36 +02:00
2024-06-16 13:39:36 +02:00
2022-04-08 14:23:58 +02:00
2022-06-09 10:23:17 +02:00
2024-06-16 13:39:36 +02:00
2024-06-16 13:39:34 +02:00
2024-06-16 13:39:40 +02:00
2024-03-26 18:21:32 -04:00
2021-03-30 18:48:56 -07:00
2022-06-09 10:23:17 +02:00
2023-03-17 08:48:50 +01:00
2023-03-17 08:48:50 +01:00
2023-03-11 13:57:26 +01:00
2021-08-23 10:25:51 -07:00
2021-08-23 10:25:51 -07:00
2021-08-23 10:25:51 -07:00
2024-06-16 13:39:36 +02:00
2024-06-16 13:39:39 +02:00
2021-06-23 01:09:35 -07:00
2024-02-23 08:54:46 +01:00
2024-06-16 13:39:36 +02:00
2023-05-11 23:00:27 +09:00
2020-12-03 00:59:26 -08:00
2024-03-26 18:21:32 -04:00
2023-06-14 11:13:00 +02:00
2023-03-11 13:57:23 +01:00
2024-01-25 14:52:27 -08:00
2020-05-26 18:56:10 -07:00