Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp277601imp; Tue, 19 Feb 2019 23:32:02 -0800 (PST) X-Google-Smtp-Source: AHgI3IY/jV0T0BaFE3CM/zZT/PsEMkYyX5GQKlh2z/aNcPZyQr+d3uMKX52UBXgjpfADhunCHqR8 X-Received: by 2002:a17:902:f096:: with SMTP id go22mr8106537plb.23.1550647922072; Tue, 19 Feb 2019 23:32:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550647922; cv=none; d=google.com; s=arc-20160816; b=ce3nJliRJlp9JoOqflbZPk6gy83/ks5qMgUAYfrm0FlMQHAvy+KKUSpWya4Q0yKIlr KoHu1OJMAa5us/DuilkgFzaUar9TnfWsg4EQBuccP4lLSU6u8NJ9vCtpJ3wgpPVU1Fmi wKJDjOwU+e+ebps6z3JVMYANHUdTSIpawLvYT+t8ZCQLbAcDhpCST5jVSl8pjCCJVzoX s4HJLrd46neQ71DTs1F3brb/e7G/l2M/ekQzrJHE0v3ash0V13za23wsxwspeUqdvkTF tK3wT1aqVjVDzf752XajwWSAnCNgqJvv700MiPNR3DDSzSSz340/xfWHiM3wRvnbP5Be uzvQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:from:subject; bh=dY9WrV8lvYhBcUXpcVdenGLbVfjZpGxzHDpKwFOTv3A=; b=SFrYcxq39cn3oRtZ84BrhalK9piNSZJpEjBtLeNvqZy2DIUto8I+kR+hRduz8aP9UI Q1PuhRL4z+VEpTF1qgn5vHSHTX8J5S9pzsuRNeoZV3JZiHxcfL0hG8612fhti4RmToXd q4lmKeXbVFmzfOwmjsnMMzwEY6a3JqgIDjaJ5KGsmMBhtuHnau5fq7+JPWGx/QcjkygW waLEdQ9y0z1gWMbqRE9BIvmECF9K8ouJ78q1a1ZvF47+0LjyQoCjXdxYEbMyYa4SVoKI GMZHmDL35fKVeKK7OkOFYao1S/AlAMV+oBFPALZHMU0ulFQoDQeSluOAuUpsK5IkHpYy YbYQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e2si7311853pgs.387.2019.02.19.23.31.45; Tue, 19 Feb 2019 23:32:02 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726516AbfBTHbX (ORCPT + 99 others); Wed, 20 Feb 2019 02:31:23 -0500 Received: from szxga07-in.huawei.com ([45.249.212.35]:58596 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725857AbfBTHbX (ORCPT ); Wed, 20 Feb 2019 02:31:23 -0500 Received: from DGGEMS414-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id BE942D01ED36AF4441CA; Wed, 20 Feb 2019 15:31:19 +0800 (CST) Received: from [127.0.0.1] (10.134.22.195) by DGGEMS414-HUB.china.huawei.com (10.3.19.214) with Microsoft SMTP Server id 14.3.408.0; Wed, 20 Feb 2019 15:31:15 +0800 Subject: Re: [f2fs-dev] [PATCH] f2fs: don't clear CP_QUOTA_NEED_FSCK_FLAG From: Chao Yu To: Jaegeuk Kim CC: , References: <20190212023343.52215-1-jaegeuk@kernel.org> <20190216045530.GA57019@jaegeuk-macbookpro.roam.corp.google.com> <29a4fd24-6340-41df-7199-6e89b70c6341@huawei.com> <20190220070855.GA91331@jaegeuk-macbookpro.roam.corp.google.com> Message-ID: <7580aa2e-b2eb-a686-a19d-4e82a713944a@huawei.com> Date: Wed, 20 Feb 2019 15:31:15 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.134.22.195] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/2/20 15:25, Chao Yu wrote: > On 2019/2/20 15:08, Jaegeuk Kim wrote: >> On 02/18, Chao Yu wrote: >>> On 2019/2/16 12:55, Jaegeuk Kim wrote: >>>> On 02/13, Chao Yu wrote: >>>>> 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 >>>>>> --- >>>>>> 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); >>>>> >>>>> I didn't get it, previously, if we didn't persist all quota file's data in >>>>> checkpoint, then we will tag CP_QUOTA_NEED_FSCK_FLAG in CP area, but in current >>>>> checkpoint, we have persisted all quota file's data, quota files are consistent >>>>> with all other files in filesystem, why we can't remove this NEED_FSCK flag..? >>>> >>>> I said it's subtle. So, I guessed 1) set CP_QUOTA_NEED_FSCK_FLAG, 2) clear >>> >>> I know it's subtle... and I agreed we can fix it like this in upstream >>> first, but in our product, it's not rare that we hit the >>> QUOTA_SKIP_FLUSH(its value is 4) case, later we may encounter long latency >>> caused by quota repairing of fsck. >>> >>>> SBI_QUOTA_SKIP_FLUSH by checkpoint, 3) clear CP_QUOTA_NEED_FSCK_FLAG by another >>>> checkpoint? >>> >>> But later if QUOTA_NEED_REPAIR is set, we will set QUOTA_NEED_FSCK_FLAG >>> again, right? >>> >>> if (is_sbi_flag_set(sbi, SBI_QUOTA_NEED_REPAIR)) >>> __set_ckpt_flags(ckpt, CP_QUOTA_NEED_FSCK_FLAG); >>> >>> >>> So in order to figure out whether this is caused by out-of-order execution >>> of below assignments: >>> >>> 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); --- clear flag later >>> >>> if (is_sbi_flag_set(sbi, SBI_QUOTA_NEED_REPAIR)) >>> __set_ckpt_flags(ckpt, CP_QUOTA_NEED_FSCK_FLAG); --- set flag first >>> >>> >>> Could you have a try: >>> >>> if (is_sbi_flag_set(sbi, SBI_QUOTA_NEED_REPAIR) || >>> 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); >> >> What does this mean? I'm in doubt we have a missing case where we clear this > > Cpu pipeline / compiler can make code out-of-order execution, which means: > > a = 1; > b = 2; > > may actually be executed as the order of: > > b = 2; > a = 1; > > So I doubt that below two line codes can be executed out-of-order: > > else > __clear_ckpt_flags(ckpt, CP_QUOTA_NEED_FSCK_FLAG); --- clear flag later > > if () > __set_ckpt_flags(ckpt, CP_QUOTA_NEED_FSCK_FLAG); --- set flag first > >> flag, CP_QUOTA_NEED_FSCK_FLAG. > > Agreed, I've checked each operation in f2fs_quota_operations yesterday, and > didn't find any missing places yet... Oh, I mean the place where set SBI_QUOTA_NEED_REPAIR, I also doubt we missed to set the flag. Thanks, > > Thanks, > >> >>> >>> Thanks, >>> >>>> >>>>> >>>>> Thanks, >>>>> >>>>>> >>>>>> if (is_sbi_flag_set(sbi, SBI_QUOTA_NEED_REPAIR)) >>>>>> __set_ckpt_flags(ckpt, CP_QUOTA_NEED_FSCK_FLAG); >>>>>> >>>> >>>> . >>>> >> >> . >> > > > > _______________________________________________ > Linux-f2fs-devel mailing list > Linux-f2fs-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel > > . >