[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250326141428.280-1-yohan.joung@sk.com>
Date: Wed, 26 Mar 2025 23:14:28 +0900
From: Yohan Joung <jyh429@...il.com>
To: jaegeuk@...nel.org,
chao@...nel.org,
daeho43@...il.com
Cc: linux-f2fs-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org,
Yohan Joung <yohan.joung@...com>
Subject: [PATCH] f2fs: prevent the current section from being selected as a victim during garbage collection
When selecting a victim using next_victim_seg in a large section, the
selected section might already have been cleared and designated as the
new current section, making it actively in use.
This behavior causes inconsistency between the SIT and SSA.
Signed-off-by: Yohan Joung <yohan.joung@...com>
---
fs/f2fs/gc.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
index 2b8f9239bede..4b5d18e395eb 100644
--- a/fs/f2fs/gc.c
+++ b/fs/f2fs/gc.c
@@ -1926,6 +1926,10 @@ int f2fs_gc(struct f2fs_sb_info *sbi, struct f2fs_gc_control *gc_control)
goto stop;
}
+ if (__is_large_section(sbi) &&
+ IS_CURSEC(sbi, GET_SEC_FROM_SEG(sbi, segno)))
+ goto stop;
+
seg_freed = do_garbage_collect(sbi, segno, &gc_list, gc_type,
gc_control->should_migrate_blocks,
gc_control->one_time);
--
2.25.1
Powered by blists - more mailing lists