projects / linux-2.6-microblaze.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: a4db59a) | patch
f2fs: stop GC when the victim becomes fully valid
authorJaegeuk Kim <jaegeuk@kernel.org>
Fri, 22 Nov 2019 20:02:06 +0000 (12:02 -0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Mon, 25 Nov 2019 18:01:28 +0000 (10:01 -0800)
commit803e74be04b32f7785742dcabfc62116718fbb06
treed25e37fca91002a47c56a452714d86f4fa0f6ef0tree | snapshot
parenta4db59ac9058207cea77df7d7893aab5c3009f87commit | diff
f2fs: stop GC when the victim becomes fully valid

We must stop GC, once the segment becomes fully valid. Otherwise, it can
produce another dirty segments by moving valid blocks in the segment partially.

Ramon hit no free segment panic sometimes and saw this case happens when
validating reliable file pinning feature.

Signed-off-by: Ramon Pantin <pantin@google.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/gc.c diff | blob | history
MicroBlaze GIT Repository