f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN

Browse source

[ Upstream commit a539363613 ]

Commit 3c6c2bebef ("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 7bc155fec5 ("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: 5460749487 ("f2fs: compress: fix to avoid inconsistence bewteen i_blocks and dnode")
Signed-off-by: Sasha Levin <sashal@kernel.org>

...

This commit is contained in:

Chao Yu 2023-12-10 17:20:35 +08:00 • committed by Sasha Levin

parent d415e1c965

commit eaf3389c85

6 changed files with 0 additions and 40 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

fs/f2fs/compress.c

View file

2

fs/f2fs/data.c

View file

6

fs/f2fs/f2fs.h

View file

3

fs/f2fs/file.c

View file

2

fs/f2fs/gc.c

View file

25

fs/f2fs/inode.c

View file