f2fs: fix to shrink gc_lock coverage in f2fs_gc_range()

Browse source

In f2fs_allocate_pinning_section(), we will hold gc_lock before calling
f2fs_gc_range() to migrate section in conventional zone, we may suffer
worse case because we may need to traverse and migrate multiple sections
if we failed to move blocks in section due to lot of reasons: ENOMEM,
fail to migrate block of pinfile, racing on i_gc_rwsem.

To avoid hold gc_lock for long time to block checkpoint, let's hold
the lock and only try to migrate one section.

Cc: Daeho Jeong <daehojeong@google.com>
Signed-off-by: Chao Yu <chao@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

...

This commit is contained in:

Chao Yu 2026-08-12 12:17:55 +00:00 • committed by Jaegeuk Kim

parent fa487f56ef

commit 5d49025a4e

4 changed files with 28 additions and 14 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/f2fs.h

View file

2

fs/f2fs/file.c

View file

34

fs/f2fs/gc.c

View file

4

fs/f2fs/segment.c

View file