From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: chao@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: accurately adjust free_sections during free_segment_range
Date: Tue, 25 Aug 2026 09:27:04 +0800 [thread overview]
Message-ID: <b3648fca-6b7f-47a4-8148-cb6748a57c46@kernel.org> (raw)
In-Reply-To: <CACOAw_wb_CPopSxjptn7MTheojQfZdtPAKh_n4OyFg9hSUbcTw@mail.gmail.com>
On 8/25/26 09:21, Daeho Jeong wrote:
> On Mon, Aug 24, 2026 at 6:05 PM Chao Yu <chao@kernel.org> wrote:
>>
>> On 8/19/26 01:14, Daeho Jeong wrote:
>>> From: Daeho Jeong <daehojeong@google.com>
>>>
>>> In free_segment_range(), MAIN_SECS(sbi) is temporarily reduced by `secs`
>>> while valid blocks in the truncated range are evacuated by GC.
>>>
>>> However, if any sections within the truncated range were already free,
>>> failing to deduct them from FREE_I(sbi)->free_sections leads to an
>>> over-estimation of available space in the reduced main area, causing
>>> inconsistent free section accounting.
>>>
>>> Fix this by calculating the number of already-free sections in the
>>> truncated range under segmap_lock, deducting them from free_sections upon
>>> entering free_segment_range(), and restoring them under segmap_lock on exit.
>>
>> I think we need to change commit message a bit to reflect real issues?
>>
>> Fixes and Cc stable line here.
>>
>>>
>>> Signed-off-by: Daeho Jeong <daehojeong@google.com>
>>> Signed-off-by: Sunmin Jeong <s_min.jeong@samsung.com>
>>> ---
>>> fs/f2fs/gc.c | 15 ++++++++++++++-
>>> 1 file changed, 14 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
>>> index 787133ee2eb2..f3a6fc6d08ae 100644
>>> --- a/fs/f2fs/gc.c
>>> +++ b/fs/f2fs/gc.c
>>> @@ -2200,8 +2200,9 @@ int f2fs_gc_range(struct f2fs_sb_info *sbi,
>>> static int free_segment_range(struct f2fs_sb_info *sbi,
>>> unsigned int secs, bool dry_run)
>>> {
>>> - unsigned int next_inuse, start, end;
>>> + unsigned int secno, next_inuse, start, end, end_secno;
>>> struct cp_control cpc = { CP_RESIZE, 0, 0, 0 };
>>> + unsigned int freed_secs = 0;
>>> int gc_mode, gc_type;
>>> int err = 0;
>>> int type;
>>> @@ -2210,6 +2211,7 @@ static int free_segment_range(struct f2fs_sb_info *sbi,
>>> MAIN_SECS(sbi) -= secs;
>>> start = MAIN_SECS(sbi) * SEGS_PER_SEC(sbi);
>>> end = MAIN_SEGS(sbi) - 1;
>>> + end_secno = GET_SEC_FROM_SEG(sbi, end);
>>>
>>> mutex_lock(&DIRTY_I(sbi)->seglist_lock);
>>> for (gc_mode = 0; gc_mode < MAX_GC_POLICY; gc_mode++)
>>> @@ -2221,6 +2223,14 @@ static int free_segment_range(struct f2fs_sb_info *sbi,
>>> sbi->next_victim_seg[gc_type] = NULL_SEGNO;
>>> mutex_unlock(&DIRTY_I(sbi)->seglist_lock);
>>>
>>> + spin_lock(&FREE_I(sbi)->segmap_lock);
>>> + for (secno = MAIN_SECS(sbi); secno <= end_secno; secno++) {
>>> + if (!test_bit(secno, FREE_I(sbi)->free_secmap))
>>> + freed_secs++;
>>> + }
>>> + FREE_I(sbi)->free_sections -= freed_secs;
>>> + spin_unlock(&FREE_I(sbi)->segmap_lock);
>>> +
>>
>> Before f2fs_gc_range
>> 0..89 have 10 dirty/full sections, 80 free sections.
>> 90..99 have 5 dirty sections, 5 free sections.
>>
>> FREE_I(sbi)->free_sections -= freed_secs;
>> free_sections = 85 - 5 = 80
>>
>> After f2fs_gc_range
>> 0..89 have 13 dirty/full sections, 77 free sections.
>> 90..99 have 10 free sections.
>> free_sections = 77 (.free_sections) + 10 (secs) = 87
>>
>>> /* Move out cursegs from the target range */
>>> for (type = CURSEG_HOT_DATA; type < NR_CURSEG_TYPE; type++) {
>>> err = f2fs_allocate_segment_for_resize(sbi, type, start, end);
>>> @@ -2245,6 +2255,9 @@ static int free_segment_range(struct f2fs_sb_info *sbi,
>>> f2fs_bug_on(sbi, 1);
>>> }
>>> out:
>>> + spin_lock(&FREE_I(sbi)->segmap_lock);
>>> + FREE_I(sbi)->free_sections += freed_secs;
>>
>> So, shouldn't be?
>> FREE_I(sbi)->free_sections += secs;
>
> During f2fs_gc_range(), when the dirty sections in 90..99 are cleaned and
> freed, `__set_test_and_free()` is invoked for those sections, which
> automatically increments `FREE_I(sbi)->free_sections` for each newly
> freed section?
Ah, I see, thanks for correcting me. :)
Thanks,
>
>>
>> Thanks,
>>
>>> + spin_unlock(&FREE_I(sbi)->segmap_lock);
>>> MAIN_SECS(sbi) += secs;
>>> return err;
>>> }
>>
prev parent reply other threads:[~2026-08-25 1:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 17:14 Daeho Jeong
2026-08-19 3:57 ` [f2fs-dev] " Chao Yu
2026-08-19 18:26 ` Daeho Jeong
2026-08-20 13:19 ` Chao Yu
2026-08-20 16:08 ` Daeho Jeong
2026-08-21 8:28 ` Yeongjin Gil
2026-08-21 16:49 ` Daeho Jeong
2026-08-22 7:31 ` Chao Yu
2026-08-24 16:49 ` Daeho Jeong
2026-08-25 1:05 ` Chao Yu
2026-08-25 1:21 ` Daeho Jeong
2026-08-25 1:27 ` Chao Yu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b3648fca-6b7f-47a4-8148-cb6748a57c46@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®