From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
Daeho Jeong <daehojeong@google.com>
Subject: Re: [PATCH] f2fs: forcibly migrate to secure space for zoned device file pinning
Date: Thu, 12 Sep 2024 14:45:56 +0000 [thread overview]
Message-ID: <ZuL-pAo6A0VVBwYG@google.com> (raw)
In-Reply-To: <20240911213031.183299-1-daeho43@gmail.com>
On 09/11, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> We need to migrate data blocks even though it is full to secure space
> for zoned device file pinning.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> Fixes: 9703d69d9d15 ("f2fs: support file pinning for zoned devices")
> ---
> fs/f2fs/gc.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> index 724bbcb447d3..aaae13493a70 100644
> --- a/fs/f2fs/gc.c
> +++ b/fs/f2fs/gc.c
> @@ -2010,8 +2010,7 @@ int f2fs_gc_range(struct f2fs_sb_info *sbi,
> .iroot = RADIX_TREE_INIT(gc_list.iroot, GFP_NOFS),
> };
>
> - do_garbage_collect(sbi, segno, &gc_list, FG_GC,
> - dry_run_sections == 0);
> + do_garbage_collect(sbi, segno, &gc_list, FG_GC, true);
Do you mean this, right?
do_garbage_collect(sbi, segno, &gc_list, FG_GC, true, false);
> put_gc_inode(&gc_list);
>
> if (!dry_run && get_valid_blocks(sbi, segno, true))
> --
> 2.46.0.598.g6f2099f65c-goog
>
next prev parent reply other threads:[~2024-09-12 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 21:30 [PATCH] f2fs: forcibly migrate to secure space for zoned device file pinning Daeho Jeong
2024-09-12 14:45 ` Jaegeuk Kim [this message]
2024-09-12 15:53 ` Daeho Jeong
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=ZuL-pAo6A0VVBwYG@google.com \
--to=jaegeuk@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