mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Chunhai Guo <guochunhai@vivo.com>, jaegeuk@kernel.org
Cc: Chao Yu <chao@kernel.org>,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] f2fs: fix missing small discard in fstrim
Date: Fri, 3 Jan 2025 11:36:03 +0800	[thread overview]
Message-ID: <b3f919fe-35a0-4253-91e9-fac8666bfbe2@kernel.org> (raw)
In-Reply-To: <20250102101310.580277-2-guochunhai@vivo.com>

On 2025/1/2 18:13, Chunhai Guo wrote:
> If userspace issues an fstrim with a range that does not include all
> segments with small discards, these segments will be reused without being

I didn't get it, if fstrim didn't cover those segments, why do we need to
issue small discard for out-of-range segments?

Thanks,

> discarded. This patch fixes this issue.
> This patch is somewhat similar to commit 650d3c4e56e1 ("f2fs: fix a missing
> discard prefree segments").
> 
> Fixes: d7bc2484b8d4 ("f2fs: fix small discards not to issue redundantly")
> Signed-off-by: Chunhai Guo <guochunhai@vivo.com>
> ---
>   fs/f2fs/segment.c | 10 +++++++---
>   1 file changed, 7 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 8fe9f794b581..af9a62591c49 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -4552,6 +4552,8 @@ void f2fs_flush_sit_entries(struct f2fs_sb_info *sbi, struct cp_control *cpc)
>   	struct list_head *head = &SM_I(sbi)->sit_entry_set;
>   	bool to_journal = !is_sbi_flag_set(sbi, SBI_IS_RESIZEFS);
>   	struct seg_entry *se;
> +	bool force = (cpc->reason & CP_DISCARD);
> +	__u64 trim_start = cpc->trim_start;
>   
>   	down_write(&sit_i->sentry_lock);
>   
> @@ -4609,7 +4611,9 @@ void f2fs_flush_sit_entries(struct f2fs_sb_info *sbi, struct cp_control *cpc)
>   #endif
>   
>   			/* add discard candidates */
> -			if (!(cpc->reason & CP_DISCARD)) {
> +			if (!force || (force &&
> +					(segno < trim_start ||
> +					 segno > cpc->trim_end))) {
>   				cpc->trim_start = segno;
>   				add_discard_addrs(sbi, cpc, false, false);
>   			}
> @@ -4649,8 +4653,8 @@ void f2fs_flush_sit_entries(struct f2fs_sb_info *sbi, struct cp_control *cpc)
>   	f2fs_bug_on(sbi, !list_empty(head));
>   	f2fs_bug_on(sbi, sit_i->dirty_sentries);
>   out:
> -	if (cpc->reason & CP_DISCARD) {
> -		__u64 trim_start = cpc->trim_start;
> +	if (force) {
> +		cpc->trim_start = trim_start;
>   
>   		for (; cpc->trim_start <= cpc->trim_end; cpc->trim_start++)
>   			add_discard_addrs(sbi, cpc, true, false);


  reply	other threads:[~2025-01-03  3:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 10:13 [PATCH 1/2] f2fs: fix missing discard candidates " Chunhai Guo
2025-01-02 10:13 ` [PATCH 2/2] f2fs: fix missing small discard " Chunhai Guo
2025-01-03  3:36   ` Chao Yu [this message]
2025-01-03  7:00     ` Chunhai Guo
2025-05-21 14:05       ` Chunhai Guo
2025-05-22  8:48       ` Chao Yu
2025-05-22 11:11   ` Chao Yu
2025-05-23  8:15     ` Chunhai Guo
2025-01-03  3:26 ` [PATCH 1/2] f2fs: fix missing discard candidates " Chao Yu
2025-01-03  8:07   ` Chunhai Guo
2025-01-08 12:46     ` Chao Yu
2025-01-09 10:03       ` Chunhai Guo
2025-01-13 13:32         ` Chao Yu
2025-01-19 13:34           ` Chunhai Guo

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=b3f919fe-35a0-4253-91e9-fac8666bfbe2@kernel.org \
    --to=chao@kernel.org \
    --cc=guochunhai@vivo.com \
    --cc=jaegeuk@kernel.org \
    --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

Powered by JetHome