f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN
authorChao Yu <chao@kernel.org>
Sun, 10 Dec 2023 09:20:35 +0000 (17:20 +0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Mon, 11 Dec 2023 21:29:34 +0000 (13:29 -0800)
commita53936361330e4c55c0654605178281387d9c761
tree70ecc77a20612d88caf793243c1abf1efc376a4c
parenta6a010f5def544af3efcfe21683905a712b60536
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>
fs/f2fs/compress.c
fs/f2fs/data.c
fs/f2fs/f2fs.h
fs/f2fs/file.c
fs/f2fs/gc.c
fs/f2fs/inode.c