Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp863773ybh; Wed, 15 Jul 2020 18:13:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyyouHaLMUIHh09JHBbj/oF7OVzvl0GDv5rLv+1PJuEnvaDje7+s0i9Hvos/0+WEaL/9btb X-Received: by 2002:a17:906:3282:: with SMTP id 2mr350235ejw.11.1594862003117; Wed, 15 Jul 2020 18:13:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594862003; cv=none; d=google.com; s=arc-20160816; b=SMjuA3CNTegXLicOmRVwWgEGR5ptq5Duy5PxIaoezKfwaaJlYewWViejeDfPe6AZrj 1smaj12dz+qXvHMS+dY/gPJhie5OIU/DFCv87KgDzqoUSsA9N4as17tKjx28+j6DWrj0 LIoTViJqq46zbfphSxHIEve27gtv6k0kGYKXcGs8sCMMqR7J09qcqMhr1djeU129vmxm MMzW11EictejfV/xnPFWxlZ7+empGl5uLvbUHQlRi1L0MnwOGnGaXstZ3kjJO0B8Gczf 7G+dupUGzgl2zVPjHTB+fKmNc1oG3OwSXuC98i8L8ZsAjROJmMPFcqchNpz3DfE14i2p ib2Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=R25QNcMQl/6qRLUXRWKILGCI4ej8qeYrjxMcX5tkU4s=; b=PZbqzTtlhKv6q4yuaNF0c1i1ip1xdSUzyMg0xW3G/FQAp7Ssj6oisRL+8QdZ8LcrWr v2rFCsPB+T8Tq1WzJlC70MXKqXSoGcMwpVZksQUU7cuoTWLHsfy/TnT+XvDSXPagiLqZ gaWPf0qjAqTmLFr8+QQ46cQLRGGl7xgX5wq/45ZxkzGllaA+OxvaykC8Fr0ebYNOEzYk kNfqoNXubHHyn6pHGzz+q0LWBwfEst8F/NyWh778jN8p5YUp7+cDQheRc7yze6b1bWJE wz3W+3Cs0BZ9k2Mbu7S3GEf8/ZJBn5HHmcCmCMhJxXGEmhDGWNOceGS/Eq7fRuE0AUZv N+1Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=UNr+Ff2g; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dt21si2209674ejb.402.2020.07.15.18.13.00; Wed, 15 Jul 2020 18:13:23 -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; dkim=pass header.i=@kernel.org header.s=default header.b=UNr+Ff2g; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726984AbgGPBKt (ORCPT + 99 others); Wed, 15 Jul 2020 21:10:49 -0400 Received: from mail.kernel.org ([198.145.29.99]:41748 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726479AbgGPBKt (ORCPT ); Wed, 15 Jul 2020 21:10:49 -0400 Received: from localhost (unknown [104.132.1.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 405AE20787; Thu, 16 Jul 2020 01:10:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1594861848; bh=jhp4R/A2lcwm+I3OFWudh5021wz4vzO9Zu9C7cuvOPo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=UNr+Ff2gwQvax/mfiG7jfCUniJPE2wjqGTfKmwuR6VV06hGXHRn1EMJlkdStw1et/ ERw18FaTpU+sp3mGzmhpj+cU4fOa1CB7JJoOqdPGbyncfcqUzVWxW+Sas+J1Ek66OX l43ogkTltrActHubBkHIc5wbpYml8ktsRYv+ikBE= Date: Wed, 15 Jul 2020 18:10:47 -0700 From: Jaegeuk Kim To: Chao Yu Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com Subject: Re: [f2fs-dev] [PATCH] f2fs: don't skip writeback of quota data Message-ID: <20200716011047.GA2540332@google.com> References: <20200709190545.GA3001066@google.com> <20200710032616.GC545837@google.com> <01d0db54-eee1-f6cd-76c3-ebe59a7abae4@huawei.com> <20200710035053.GH545837@google.com> <77041117-f615-e6e6-591c-b02bf99e58c2@huawei.com> <20200713175926.GB2910046@google.com> <20200715191037.GB2232118@google.com> <4edac8af-0ae8-65e1-e3a0-a633cf81d761@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4edac8af-0ae8-65e1-e3a0-a633cf81d761@huawei.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/16, Chao Yu wrote: > On 2020/7/16 3:10, Jaegeuk Kim wrote: > > On 07/14, Chao Yu wrote: > >> On 2020/7/14 1:59, Jaegeuk Kim wrote: > >>> On 07/10, Chao Yu wrote: > >>>> On 2020/7/10 11:50, Jaegeuk Kim wrote: > >>>>> On 07/10, Chao Yu wrote: > >>>>>> On 2020/7/10 11:26, Jaegeuk Kim wrote: > >>>>>>> On 07/10, Chao Yu wrote: > >>>>>>>> On 2020/7/10 3:05, Jaegeuk Kim wrote: > >>>>>>>>> On 07/09, Chao Yu wrote: > >>>>>>>>>> On 2020/7/9 13:30, Jaegeuk Kim wrote: > >>>>>>>>>>> It doesn't need to bypass flushing quota data in background. > >>>>>>>>>> > >>>>>>>>>> The condition is used to flush quota data in batch to avoid random > >>>>>>>>>> small-sized udpate, did you hit any problem here? > >>>>>>>>> > >>>>>>>>> I suspect this causes fault injection test being stuck by waiting for inode > >>>>>>>>> writeback completion. With this patch, it has been running w/o any issue so far. > >>>>>>>>> I keep an eye on this. > >>>>>>>> > >>>>>>>> Hmmm.. so that this patch may not fix the root cause, and it may hiding the > >>>>>>>> issue deeper. > >>>>>>>> > >>>>>>>> How about just keeping this patch in our private branch to let fault injection > >>>>>>>> test not be stuck? until we find the root cause in upstream codes. > >>>>>>> > >>>>>>> Well, I don't think this hides something. When the issue happens, I saw inodes > >>>>>>> being stuck due to writeback while only quota has some dirty data. At that time, > >>>>>>> there was no dirty data page from other inodes. > >>>>>> > >>>>>> Okay, > >>>>>> > >>>>>>> > >>>>>>> More specifically, I suspect __writeback_inodes_sb_nr() gives WB_SYNC_NONE and > >>>>>>> waits for wb_wait_for_completion(). > >>>>>> > >>>>>> Did you record any callstack after the issue happened? > >>>>> > >>>>> I found this. > >>>>> > >>>>> [213389.297642] __schedule+0x2dd/0x780^M > >>>>> [213389.299224] schedule+0x55/0xc0^M > >>>>> [213389.300745] wb_wait_for_completion+0x56/0x90^M > >>>>> [213389.302469] ? wait_woken+0x80/0x80^M > >>>>> [213389.303997] __writeback_inodes_sb_nr+0xa8/0xd0^M > >>>>> [213389.305760] writeback_inodes_sb+0x4b/0x60^M > >>>>> [213389.307439] sync_filesystem+0x2e/0xa0^M > >>>>> [213389.308999] generic_shutdown_super+0x27/0x110^M > >>>>> [213389.310738] kill_block_super+0x27/0x50^M > >>>>> [213389.312327] kill_f2fs_super+0x76/0xe0 [f2fs]^M > >>>>> [213389.314014] deactivate_locked_super+0x3b/0x80^M > >>>>> [213389.315692] deactivate_super+0x3e/0x50^M > >>>>> [213389.317226] cleanup_mnt+0x109/0x160^M > >>>>> [213389.318718] __cleanup_mnt+0x12/0x20^M > >>>>> [213389.320177] task_work_run+0x70/0xb0^M > >>>>> [213389.321609] exit_to_usermode_loop+0x131/0x160^M > >>>>> [213389.323306] do_syscall_64+0x170/0x1b0^M > >>>>> [213389.324762] entry_SYSCALL_64_after_hwframe+0x44/0xa9^M > >>>>> [213389.326477] RIP: 0033:0x7fc4b5e6a35b^M > >>>> > >>>> Does this only happen during umount? If so, will below change help? > >>>> > >>>> if ((S_ISDIR(inode->i_mode) || IS_NOQUOTA(inode)) && > >>>> + !is_sbi_flag_set(sbi, SBI_IS_CLOSE) && > >>>> wbc->sync_mode == WB_SYNC_NONE && > >>>> get_dirty_pages(inode) < nr_pages_to_skip(sbi, DATA) && > >>>> f2fs_available_free_memory(sbi, DIRTY_DENTS)) > >>>> goto skip_write; > >>> > >>> Hmm, this doesn't work. The writeback was called before put_super? > >> > >> Oops, still be confused about this issue. :( > > > > Huam, I hit the problem with the patch. > > I need to return back and think in other way. :( > > Still quota data was left? what about dentry? Huh, at this time, only node and meta pages were left as dirty. > > Thanks, > > > > >> > >> Thanks, > >> > >>> I'll try the original patch one more time. > >>> > >>>> > >>>>> > >>>>>> > >>>>>> Still I'm confused that why directory's data written could be skipped, but > >>>>>> quota's data couldn't, what's the difference? > >>>>> > >>>>> I suspect different blocking timing from cp_error between quota and dentry. > >>>>> e.g., we block dir operations right after cp_error, while quota can make > >>>> > >>>> No guarantee that there is no dirty dentry being created after > >>>> cp_error, right? > >>>> > >>>> e.g. > >>>> > >>>> Thread A Thread B > >>>> - f2fs_create > >>>> - bypass f2fs_cp_error > >>>> - set cp_error > >>>> - create dirty dentry > >>>> > >>>> BTW, do you know what __writeback_inodes_sb_nr is waiting for? > >>>> > >>>>> dirty pages in more fine granularity. > >>>>> > >>>>>> > >>>>>>> > >>>>>>>> > >>>>>>>> Thanks, > >>>>>>>> > >>>>>>>>> > >>>>>>>>> Thanks, > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Thanks, > >>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> Signed-off-by: Jaegeuk Kim > >>>>>>>>>>> --- > >>>>>>>>>>> fs/f2fs/data.c | 2 +- > >>>>>>>>>>> 1 file changed, 1 insertion(+), 1 deletion(-) > >>>>>>>>>>> > >>>>>>>>>>> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c > >>>>>>>>>>> index 44645f4f914b6..72e8b50e588c1 100644 > >>>>>>>>>>> --- a/fs/f2fs/data.c > >>>>>>>>>>> +++ b/fs/f2fs/data.c > >>>>>>>>>>> @@ -3148,7 +3148,7 @@ static int __f2fs_write_data_pages(struct address_space *mapping, > >>>>>>>>>>> if (unlikely(is_sbi_flag_set(sbi, SBI_POR_DOING))) > >>>>>>>>>>> goto skip_write; > >>>>>>>>>>> > >>>>>>>>>>> - if ((S_ISDIR(inode->i_mode) || IS_NOQUOTA(inode)) && > >>>>>>>>>>> + if (S_ISDIR(inode->i_mode) && > >>>>>>>>>>> wbc->sync_mode == WB_SYNC_NONE && > >>>>>>>>>>> get_dirty_pages(inode) < nr_pages_to_skip(sbi, DATA) && > >>>>>>>>>>> f2fs_available_free_memory(sbi, DIRTY_DENTS)) > >>>>>>>>>>> > >>>>>>>>> . > >>>>>>>>> > >>>>>>> . > >>>>>>> > >>>>> . > >>>>> > >>> . > >>> > > . > >