diff options
| author | Chao Yu <chao@kernel.org> | 2023-12-10 17:20:35 +0800 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2023-12-11 13:29:34 -0800 |
| commit | a53936361330e4c55c0654605178281387d9c761 (patch) | |
| tree | 70ecc77a20612d88caf793243c1abf1efc376a4c /fs/f2fs/file.c | |
| parent | a6a010f5def544af3efcfe21683905a712b60536 (diff) | |
| download | linux-a53936361330e4c55c0654605178281387d9c761.tar.gz linux-a53936361330e4c55c0654605178281387d9c761.tar.bz2 linux-a53936361330e4c55c0654605178281387d9c761.zip | |
f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN
Commit 3c6c2bebef79 ("f2fs: avoid punch_hole overhead when releasing
volatile data") introduced FI_FIRST_BLOCK_WRITTEN as below reason:
This patch is to avoid some punch_hole overhead when releasing volatile
data. If volatile data was not written yet, we just can make the first
page as zero.
After commit 7bc155fec5b3 ("f2fs: kill volatile write support"), we
won't support volatile write, but it missed to remove obsolete
FI_FIRST_BLOCK_WRITTEN, delete it in this patch.
Signed-off-by: Chao Yu <chao@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/file.c')
| -rw-r--r-- | fs/f2fs/file.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index 325dab01a29d..5025abf2d995 100644 --- a/fs/f2fs/file.c +++ b/fs/f2fs/file.c @@ -599,9 +599,6 @@ void f2fs_truncate_data_blocks_range(struct dnode_of_data *dn, int count) valid_blocks++; } - if (dn->ofs_in_node == 0 && IS_INODE(dn->node_page)) - clear_inode_flag(dn->inode, FI_FIRST_BLOCK_WRITTEN); - f2fs_invalidate_blocks(sbi, blkaddr); if (!released || blkaddr != COMPRESS_ADDR) |