Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp433554ybm; Tue, 26 May 2020 22:09:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz9LlTRLpHGMchkmNCCn5iUevYDTEwEdhGQ12v2jGnF8LQujwvu+MadnyNMP+yTY8WKV41v X-Received: by 2002:aa7:d284:: with SMTP id w4mr22520442edq.223.1590556161442; Tue, 26 May 2020 22:09:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590556161; cv=none; d=google.com; s=arc-20160816; b=VYmyoDJxgeMuixArt7V3L3hn8AVLcJssy+uIDzgsplQl0PV7kF3ovH2gdsMPfH5eB5 KzVc7fNTy8wUA/LbOkjWVy64HI1MdWpehh7mOhji/yetbd3WIxB3ZUvx4ZeyGbndabvX FuZP8eQeP0IcIWwEhRFNmoJ4scAn14SB8zLaG2dm6w+VJm9u6tTrOyytcxTfZqgcPLbs y19x1H2P1KQpOOp8SCze2NkTFZ8VF8sieB6bAcArPcGUc4zWFM1MXqT4OEpJBRufzP/I MDDgqYVlF20oLwGzHx1vsJmlIN6HduWO7/0JDhNaCZ4Wtgh4Ktln+8AekyAx9C5Rs5I/ juTw== 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:from:references:cc:to:subject; bh=ECvW5mzt381sRa6btTvwKp66UY4TyyiEt3pCB1FSamI=; b=sBo8brnw6cVnlXm1FQQu4zko4LsLg24mIs1gQw/dlsOA1MDXhrPdPTsISOyuspLnwu ia7fBxz9nW4TkQL+2Sx7aWmN2iTQc51pZSaO06d7Yo+k+Y1CVsdSzLcD+jHvmv0ip/yD U4AGKYPABLUgh4PmceWjizc5W7gPDOYSQ90vCIirJqIaBoLbRlXjodTuzdndUeWie7r7 xXblEfwUzbHe+k4WK3XDWVforz7O88tDOcO63sOGgFrPGhMATwGX4sdChKK4uMZghElR fOZ6iQCz4k0n1Wpq9uJu507gQZOFueotmM8H6kpFEoOkHZuzRsAqDVSRcrJ3Ma5TCxhC q6rg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u6si981691edx.460.2020.05.26.22.08.58; Tue, 26 May 2020 22:09:21 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726846AbgE0Cfi (ORCPT + 99 others); Tue, 26 May 2020 22:35:38 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:5285 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725601AbgE0Cfi (ORCPT ); Tue, 26 May 2020 22:35:38 -0400 Received: from DGGEMS404-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 3A84687391F412890586; Wed, 27 May 2020 10:35:36 +0800 (CST) Received: from [10.134.22.195] (10.134.22.195) by smtp.huawei.com (10.3.19.204) with Microsoft SMTP Server (TLS) id 14.3.487.0; Wed, 27 May 2020 10:35:35 +0800 Subject: Re: [f2fs-dev] [PATCH v3] f2fs: avoid inifinite loop to wait for flushing node pages at cp_error To: Jaegeuk Kim CC: , , References: <20200522144752.216197-1-jaegeuk@kernel.org> <20200522233243.GA94020@google.com> <20200525035655.GA135148@google.com> <565af47c-8364-d910-8d1c-93645c12e660@huawei.com> <20200525150608.GA55033@google.com> <92afae8b-2dd3-171a-562c-404a67f9aab2@huawei.com> <20200526015650.GA207949@google.com> From: Chao Yu Message-ID: <765a1ac5-a318-14d6-666f-eab46f892d01@huawei.com> Date: Wed, 27 May 2020 10:35:35 +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: <20200526015650.GA207949@google.com> 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 2020/5/26 9:56, Jaegeuk Kim wrote: > On 05/26, Chao Yu wrote: >> On 2020/5/26 9:11, Chao Yu wrote: >>> On 2020/5/25 23:06, Jaegeuk Kim wrote: >>>> On 05/25, Chao Yu wrote: >>>>> On 2020/5/25 11:56, Jaegeuk Kim wrote: >>>>>> Shutdown test is somtimes hung, since it keeps trying to flush dirty node pages 71.07% 0.01% kworker/u256:1+ [kernel.kallsyms] [k] wb_writeback | --71.06%--wb_writeback | |--68.96%--__writeback_inodes_wb | | | --68.95%--writeback_sb_inodes | | | |--65.08%--__writeback_single_inode | | | | | --64.35%--do_writepages | | | | | |--59.83%--f2fs_write_node_pages | | | | | | | --59.74%--f2fs_sync_node_pages | | | | | | | |--27.91%--pagevec_lookup_range_tag | | | | | | | | | --27.90%--find_get_pages_range_tag Before umount, kworker will always hold one core, that looks not reasonable, to avoid that, could we just allow node write, since it's out-place-update, and cp is not allowed, we don't need to worry about its effect on data on previous checkpoint, and it can decrease memory footprint cost by node pages. Thanks, >>>>> >>>>> IMO, for umount case, we should drop dirty reference and dirty pages on meta/data >>>>> pages like we change for node pages to avoid potential dead loop... >>>> >>>> I believe we're doing for them. :P >>> >>> Actually, I mean do we need to drop dirty meta/data pages explicitly as below: >>> >>> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c >>> index 3dc3ac6fe143..4c08fd0a680a 100644 >>> --- a/fs/f2fs/checkpoint.c >>> +++ b/fs/f2fs/checkpoint.c >>> @@ -299,8 +299,15 @@ static int __f2fs_write_meta_page(struct page *page, >>> >>> trace_f2fs_writepage(page, META); >>> >>> - if (unlikely(f2fs_cp_error(sbi))) >>> + if (unlikely(f2fs_cp_error(sbi))) { >>> + if (is_sbi_flag_set(sbi, SBI_IS_CLOSE)) { >>> + ClearPageUptodate(page); >>> + dec_page_count(sbi, F2FS_DIRTY_META); >>> + unlock_page(page); >>> + return 0; >>> + } >>> goto redirty_out; >>> + } >>> if (unlikely(is_sbi_flag_set(sbi, SBI_POR_DOING))) >>> goto redirty_out; >>> if (wbc->for_reclaim && page->index < GET_SUM_BLOCK(sbi, 0)) >>> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c >>> index 48a622b95b76..94b342802513 100644 >>> --- a/fs/f2fs/data.c >>> +++ b/fs/f2fs/data.c >>> @@ -2682,6 +2682,12 @@ int f2fs_write_single_data_page(struct page *page, int *submitted, >>> >>> /* we should bypass data pages to proceed the kworkder jobs */ >>> if (unlikely(f2fs_cp_error(sbi))) { >>> + if (is_sbi_flag_set(sbi, SBI_IS_CLOSE)) { >>> + ClearPageUptodate(page); >>> + inode_dec_dirty_pages(inode); >>> + unlock_page(page); >>> + return 0; >>> + } >> >> Oh, I notice previously, we will drop non-directory inode's dirty pages directly, >> however, during umount, we'd better drop directory inode's dirty pages as well, right? > > Hmm, I remember I dropped them before. Need to double check. > >> >>> mapping_set_error(page->mapping, -EIO); >>> /* >>> * don't drop any dirty dentry pages for keeping lastest >>> >>>> >>>>> >>>>> Thanks, >>>>> >>>>>> in an inifinite loop. Let's drop dirty pages at umount in that case. >>>>>> >>>>>> Signed-off-by: Jaegeuk Kim >>>>>> --- >>>>>> v3: >>>>>> - fix wrong unlock >>>>>> >>>>>> v2: >>>>>> - fix typos >>>>>> >>>>>> fs/f2fs/node.c | 9 ++++++++- >>>>>> 1 file changed, 8 insertions(+), 1 deletion(-) >>>>>> >>>>>> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c >>>>>> index e632de10aedab..e0bb0f7e0506e 100644 >>>>>> --- a/fs/f2fs/node.c >>>>>> +++ b/fs/f2fs/node.c >>>>>> @@ -1520,8 +1520,15 @@ static int __write_node_page(struct page *page, bool atomic, bool *submitted, >>>>>> >>>>>> trace_f2fs_writepage(page, NODE); >>>>>> >>>>>> - if (unlikely(f2fs_cp_error(sbi))) >>>>>> + if (unlikely(f2fs_cp_error(sbi))) { >>>>>> + if (is_sbi_flag_set(sbi, SBI_IS_CLOSE)) { >>>>>> + ClearPageUptodate(page); >>>>>> + dec_page_count(sbi, F2FS_DIRTY_NODES); >>>>>> + unlock_page(page); >>>>>> + return 0; >>>>>> + } >>>>>> goto redirty_out; >>>>>> + } >>>>>> >>>>>> if (unlikely(is_sbi_flag_set(sbi, SBI_POR_DOING))) >>>>>> goto redirty_out; >>>>>> >>>> . >>>> >>> >>> >>> _______________________________________________ >>> Linux-f2fs-devel mailing list >>> Linux-f2fs-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel >>> . >>> > . >