From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/5 v2] f2fs: check number of blocks in a current section
Date: Tue, 27 Feb 2024 14:08:33 +0800 [thread overview]
Message-ID: <be97cea3-fb46-4c87-b858-e28f31bfa45c@kernel.org> (raw)
In-Reply-To: <Zd0bUnFCWmPtwK2u@google.com>
On 2024/2/27 7:14, Jaegeuk Kim wrote:
> In cfd66bb715fd ("f2fs: fix deadloop in foreground GC"), we needed to check
> the number of blocks in a section instead of the segment.
>
> Fixes: cfd66bb715fd ("f2fs: fix deadloop in foreground GC")
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/5 v2] f2fs: check number of blocks in a current section
Date: Tue, 27 Feb 2024 14:08:33 +0800 [thread overview]
Message-ID: <be97cea3-fb46-4c87-b858-e28f31bfa45c@kernel.org> (raw)
In-Reply-To: <Zd0bUnFCWmPtwK2u@google.com>
On 2024/2/27 7:14, Jaegeuk Kim wrote:
> In cfd66bb715fd ("f2fs: fix deadloop in foreground GC"), we needed to check
> the number of blocks in a section instead of the segment.
>
> Fixes: cfd66bb715fd ("f2fs: fix deadloop in foreground GC")
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-02-27 6:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 20:55 [PATCH 1/5] f2fs: check number of blocks in a current section Jaegeuk Kim
2024-02-23 20:55 ` [f2fs-dev] " Jaegeuk Kim
2024-02-23 20:55 ` [PATCH 2/5] f2fs: fix write pointers all the time Jaegeuk Kim
2024-02-23 20:55 ` [f2fs-dev] " Jaegeuk Kim
2024-02-26 2:48 ` Chao Yu
2024-02-26 2:48 ` Chao Yu
2024-02-26 17:33 ` Daeho Jeong
2024-02-26 17:33 ` Daeho Jeong
2024-02-27 1:00 ` Jaegeuk Kim
2024-02-27 1:00 ` Jaegeuk Kim
2024-02-27 0:59 ` [PATCH 2/5 v2] " Jaegeuk Kim
2024-02-27 0:59 ` [f2fs-dev] " Jaegeuk Kim
2024-02-27 6:19 ` Chao Yu
2024-02-27 6:19 ` Chao Yu
2024-02-23 20:55 ` [PATCH 3/5] f2fs: print zone status in string and some log Jaegeuk Kim
2024-02-23 20:55 ` [f2fs-dev] " Jaegeuk Kim
2024-02-26 2:54 ` Chao Yu
2024-02-26 2:54 ` Chao Yu
2024-02-26 19:03 ` Daeho Jeong
2024-02-26 19:03 ` Daeho Jeong
2024-02-26 22:52 ` [PATCH 3/5 v2] " Jaegeuk Kim
2024-02-26 22:52 ` [f2fs-dev] " Jaegeuk Kim
2024-02-27 6:26 ` Chao Yu
2024-02-27 6:26 ` Chao Yu
2024-03-04 17:47 ` [PATCH 3/5] " Jaegeuk Kim
2024-03-04 17:47 ` [f2fs-dev] " Jaegeuk Kim
2024-02-23 20:55 ` [PATCH 4/5] f2fs: prevent an f2fs_gc loop during disable_checkpoint Jaegeuk Kim
2024-02-23 20:55 ` [f2fs-dev] " Jaegeuk Kim
2024-02-26 2:58 ` Chao Yu
2024-02-26 2:58 ` Chao Yu
2024-02-26 19:14 ` Daeho Jeong
2024-02-26 19:14 ` Daeho Jeong
2024-02-23 20:55 ` [PATCH 5/5] f2fs: allow to mount if cap is 100 Jaegeuk Kim
2024-02-23 20:55 ` [f2fs-dev] " Jaegeuk Kim
2024-02-26 2:59 ` Chao Yu
2024-02-26 2:59 ` Chao Yu
2024-02-26 19:34 ` Daeho Jeong
2024-02-26 19:34 ` Daeho Jeong
2024-02-26 22:47 ` Jaegeuk Kim
2024-02-26 22:47 ` Jaegeuk Kim
2024-02-28 3:47 ` Daeho Jeong
2024-02-28 3:47 ` Daeho Jeong
2024-02-26 2:40 ` [f2fs-dev] [PATCH 1/5] f2fs: check number of blocks in a current section Chao Yu
2024-02-26 2:40 ` Chao Yu
2024-02-26 17:17 ` Daeho Jeong
2024-02-26 17:17 ` Daeho Jeong
2024-02-26 23:14 ` [PATCH 1/5 v2] " Jaegeuk Kim
2024-02-26 23:14 ` [f2fs-dev] " Jaegeuk Kim
2024-02-27 6:08 ` Chao Yu [this message]
2024-02-27 6:08 ` Chao Yu
2024-02-28 22:50 ` [f2fs-dev] [PATCH 1/5] " patchwork-bot+f2fs
2024-02-28 22:50 ` patchwork-bot+f2fs
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=be97cea3-fb46-4c87-b858-e28f31bfa45c@kernel.org \
--to=chao@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.