]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN
authorChao Yu <chao@kernel.org>
Sun, 10 Dec 2023 09:20:35 +0000 (17:20 +0800)
committerSasha Levin <sashal@kernel.org>
Tue, 26 Mar 2024 22:19:59 +0000 (18:19 -0400)
commiteaf3389c8545487c520d104f9596d810e51301bb
tree468d39455ff0396d005f1631ddfe7551bc1ae0d9
parentd415e1c965992e9bffa32c7dbf9143ca2ce884ae
f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN

[ Upstream commit a53936361330e4c55c0654605178281387d9c761 ]

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>
Stable-dep-of: 54607494875e ("f2fs: compress: fix to avoid inconsistence bewteen i_blocks and dnode")
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/f2fs/compress.c
fs/f2fs/data.c
fs/f2fs/f2fs.h
fs/f2fs/file.c
fs/f2fs/gc.c
fs/f2fs/inode.c