lkml.org 
[lkml]   [2022]   [Oct]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5.10 389/390] f2fs: fix wrong condition to trigger background checkpoint correctly
    Date
    From: Chao Yu <chao@kernel.org>

    commit cd6d697a6e2013a0a85f8b261b16c8cfd50c1f5f upstream.

    In f2fs_balance_fs_bg(), it needs to check both NAT_ENTRIES and INO_ENTRIES
    memory usage to decide whether we should skip background checkpoint, otherwise
    we may always skip checking INO_ENTRIES memory usage, so that INO_ENTRIES may
    potentially cause high memory footprint.

    Fixes: 493720a48543 ("f2fs: fix to avoid REQ_TIME and CP_TIME collision")
    Signed-off-by: Chao Yu <chao@kernel.org>
    Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    ---
    fs/f2fs/segment.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    --- a/fs/f2fs/segment.c
    +++ b/fs/f2fs/segment.c
    @@ -550,7 +550,7 @@ void f2fs_balance_fs_bg(struct f2fs_sb_i
    goto do_sync;

    /* checkpoint is the only way to shrink partial cached entries */
    - if (f2fs_available_free_memory(sbi, NAT_ENTRIES) ||
    + if (f2fs_available_free_memory(sbi, NAT_ENTRIES) &&
    f2fs_available_free_memory(sbi, INO_ENTRIES))
    return;


    \
     
     \ /
      Last update: 2022-10-24 15:39    [W:4.072 / U:0.136 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site