From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't clear CP_QUOTA_NEED_FSCK_FLAG
Date: Fri, 10 May 2019 17:45:14 +0800 [thread overview]
Message-ID: <5ee36ad7-9fe9-adcf-0974-5c17fa8d50ee@huawei.com> (raw)
In-Reply-To: <20190212023343.52215-1-jaegeuk@kernel.org>
On 2019/2/12 10:33, Jaegeuk Kim wrote:
> If we met this once, let fsck.f2fs clear this only.
> Note that, this addresses all the subtle fault injection test.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/checkpoint.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
> index 03fea4efd64b..10a3ada28715 100644
> --- a/fs/f2fs/checkpoint.c
> +++ b/fs/f2fs/checkpoint.c
> @@ -1267,8 +1267,6 @@ static void update_ckpt_flags(struct f2fs_sb_info *sbi, struct cp_control *cpc)
>
> if (is_sbi_flag_set(sbi, SBI_QUOTA_SKIP_FLUSH))
> __set_ckpt_flags(ckpt, CP_QUOTA_NEED_FSCK_FLAG);
> - else
> - __clear_ckpt_flags(ckpt, CP_QUOTA_NEED_FSCK_FLAG);
Jaegeuk,
Will below commit fix this issue? Not sure, but just want to check that.. :)
f2fs-tools: fix to check total valid block count before block allocation
Thanks,
>
> if (is_sbi_flag_set(sbi, SBI_QUOTA_NEED_REPAIR))
> __set_ckpt_flags(ckpt, CP_QUOTA_NEED_FSCK_FLAG);
>
next prev parent reply other threads:[~2019-05-10 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 2:33 Jaegeuk Kim
2019-02-13 3:42 ` [f2fs-dev] " Chao Yu
2019-02-16 4:55 ` Jaegeuk Kim
2019-02-18 9:10 ` Chao Yu
2019-02-20 7:08 ` Jaegeuk Kim
2019-02-20 7:25 ` Chao Yu
2019-02-20 7:31 ` Chao Yu
2019-02-22 2:40 ` Jaegeuk Kim
2019-02-22 3:27 ` Chao Yu
2019-02-26 17:57 ` Jaegeuk Kim
2019-02-28 1:08 ` Chao Yu
2019-05-10 9:45 ` Chao Yu [this message]
2019-05-20 23:24 ` Jaegeuk Kim
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=5ee36ad7-9fe9-adcf-0974-5c17fa8d50ee@huawei.com \
--to=yuchao0@huawei.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
all inboxes | Powered by JetHome®