diff options
author | Sahitya Tummala <stummala@codeaurora.org> | 2019-07-29 10:50:26 +0530 |
---|---|---|
committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2019-09-09 13:06:11 +0100 |
commit | 957fa47823dfe449c5a15a944e4e7a299a6601db (patch) | |
tree | a58f58dbf5ce86e54f670308baa03326abcb2d8b /tools/perf/scripts/python/export-to-postgresql.py | |
parent | cfb9a34d147b8d002d4330ddb53a3eb79565d17c (diff) |
f2fs: Fix indefinite loop in f2fs_gc()
Policy - foreground GC, LFS mode and greedy GC mode.
Under this policy, f2fs_gc() loops forever to GC as it doesn't have
enough free segements to proceed and thus it keeps calling gc_more
for the same victim segment. This can happen if the selected victim
segment could not be GC'd due to failed blkaddr validity check i.e.
is_alive() returns false for the blocks set in current validity map.
Fix this by not resetting the sbi->cur_victim_sec to NULL_SEGNO, when
the segment selected could not be GC'd. This helps to select another
segment for GC and thus helps to proceed forward with GC.
[Note]
This can happen due to is_alive as well as atomic_file which skipps
GC.
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions