From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] f2fs: fix to don't call f2fs_stop_checkpoint in spinlock coverage
Date: Wed, 28 Feb 2024 09:23:05 +0800 [thread overview]
Message-ID: <bdacbc3c-87c0-42b7-980b-9f9830ab994c@kernel.org> (raw)
In-Reply-To: <Zd4g2SgQn3v_ZJMj@google.com>
On 2024/2/28 1:50, Jaegeuk Kim wrote:
> On 02/22, Chao Yu wrote:
>> f2fs_stop_checkpoint(, false) is complex and it may sleep, so we should
>> move it outside segmap_lock spinlock coverage in get_new_segment().
>
> Chao, I merged this patch into
>
> https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev-test&id=f3b576d209983b5d6e1cb130bfc8ca1f0bbcad6d
It's fine to me.
Thanks,
>
>>
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>> fs/f2fs/segment.c | 12 +++++++++---
>> 1 file changed, 9 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
>> index d0209ea77dd2..8edc42071e6f 100644
>> --- a/fs/f2fs/segment.c
>> +++ b/fs/f2fs/segment.c
>> @@ -2646,6 +2646,7 @@ static void get_new_segment(struct f2fs_sb_info *sbi,
>> unsigned int old_zoneno = GET_ZONE_FROM_SEG(sbi, *newseg);
>> bool init = true;
>> int i;
>> + int ret = 0;
>>
>> spin_lock(&free_i->segmap_lock);
>>
>> @@ -2671,9 +2672,8 @@ static void get_new_segment(struct f2fs_sb_info *sbi,
>> secno = find_first_zero_bit(free_i->free_secmap,
>> MAIN_SECS(sbi));
>> if (secno >= MAIN_SECS(sbi)) {
>> - f2fs_stop_checkpoint(sbi, false,
>> - STOP_CP_REASON_NO_SEGMENT);
>> - f2fs_bug_on(sbi, 1);
>> + ret = -ENOSPC;
>> + goto out_unlock;
>> }
>> }
>> segno = GET_SEG_FROM_SEC(sbi, secno);
>> @@ -2704,7 +2704,13 @@ static void get_new_segment(struct f2fs_sb_info *sbi,
>> f2fs_bug_on(sbi, test_bit(segno, free_i->free_segmap));
>> __set_inuse(sbi, segno);
>> *newseg = segno;
>> +out_unlock:
>> spin_unlock(&free_i->segmap_lock);
>> +
>> + if (ret) {
>> + f2fs_stop_checkpoint(sbi, false, STOP_CP_REASON_NO_SEGMENT);
>> + f2fs_bug_on(sbi, 1);
>> + }
>> }
>>
>> static void reset_curseg(struct f2fs_sb_info *sbi, int type, int modified)
>> --
>> 2.40.1
next prev parent reply other threads:[~2024-02-28 1:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 12:18 [PATCH 1/4] f2fs: delete f2fs_get_new_segment() declaration Chao Yu
2024-02-22 12:18 ` [PATCH 2/4] f2fs: fix to don't call f2fs_stop_checkpoint in spinlock coverage Chao Yu
2024-02-27 17:50 ` Jaegeuk Kim
2024-02-28 1:23 ` Chao Yu [this message]
2024-02-22 12:18 ` [PATCH 3/4] f2fs: fix to handle segment allocation failure correctly Chao Yu
2024-02-26 7:46 ` Chao Yu
2024-02-26 10:28 ` Zhiguo Niu
2024-02-22 12:18 ` [PATCH 4/4] f2fs: introduce FAULT_NO_SEGMENT Chao Yu
2024-02-28 22:50 ` [f2fs-dev] [PATCH 1/4] f2fs: delete f2fs_get_new_segment() declaration 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=bdacbc3c-87c0-42b7-980b-9f9830ab994c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome