From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: let background GC being aware of freezing
Date: Sat, 22 Jul 2017 08:47:45 +0800 [thread overview]
Message-ID: <e76e01ba-8bee-e9fb-62e2-ed411336a68b@kernel.org> (raw)
In-Reply-To: <20170721205418.GA14361@jaegeuk-macbookpro.roam.corp.google.com>
Hi Jaegeuk,
On 2017/7/22 4:54, Jaegeuk Kim wrote:
> Hi Chao,
>
> On 07/21, Chao Yu wrote:
>> When ->freeze_fs is called from lvm for doing snapshot, it needs to
>> make sure there will be no more changes in filesystem's data, however,
>> previously, background GC wasn't aware of freezing, so in environment
>> with active background GC thread, data of snapshot becomes unstable.
>
> What about flush/discard threads?
Updated.
Thanks,
>
> Thanks,
>
>>
>> This patch fixes this issue by adding sb_{start,end}_intwrite in GC
>> flow.
>>
>> Signed-off-by: Chao Yu <yuchao0@huawei.com>
>> ---
>> fs/f2fs/gc.c | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
>> index 76ad2c3d88db..1c0117f60083 100644
>> --- a/fs/f2fs/gc.c
>> +++ b/fs/f2fs/gc.c
>> @@ -55,6 +55,8 @@ static int gc_thread_func(void *data)
>> }
>> #endif
>>
>> + sb_start_intwrite(sbi->sb);
>> +
>> /*
>> * [GC triggering condition]
>> * 0. GC is not conducted currently.
>> @@ -69,12 +71,12 @@ static int gc_thread_func(void *data)
>> * So, I'd like to wait some time to collect dirty segments.
>> */
>> if (!mutex_trylock(&sbi->gc_mutex))
>> - continue;
>> + goto next;
>>
>> if (!is_idle(sbi)) {
>> increase_sleep_time(gc_th, &wait_ms);
>> mutex_unlock(&sbi->gc_mutex);
>> - continue;
>> + goto next;
>> }
>>
>> if (has_enough_invalid_blocks(sbi))
>> @@ -93,6 +95,8 @@ static int gc_thread_func(void *data)
>>
>> /* balancing f2fs's metadata periodically */
>> f2fs_balance_fs_bg(sbi);
>> +next:
>> + sb_end_intwrite(sbi->sb);
>>
>> } while (!kthread_should_stop());
>> return 0;
>> --
>> 2.13.1.388.g69e6b9b4f4a9
prev parent reply other threads:[~2017-07-22 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 3:36 [PATCH] f2fs: let background GC being aware of freezing Chao Yu
2017-07-21 20:54 ` Jaegeuk Kim
2017-07-22 0:47 ` Chao Yu [this message]
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=e76e01ba-8bee-e9fb-62e2-ed411336a68b@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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