Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp4351618ybe; Mon, 9 Sep 2019 08:06:53 -0700 (PDT) X-Google-Smtp-Source: APXvYqwgg5YANAI3rYMkfZM9dUEse/PSuoOUQUST1eJpiPUC7uobVwk6KXaeiRgvpBr5qQS44AUb X-Received: by 2002:a1c:7ecf:: with SMTP id z198mr18684781wmc.175.1568041613545; Mon, 09 Sep 2019 08:06:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568041613; cv=none; d=google.com; s=arc-20160816; b=QeIJXFQC3Qy6nyMfgdyNHpRO3vILAvDVWDTlihl255SmwSvp9oE8jP1M7Nt1wSm3/b +oc4LpTLrNgFi37jfKDSzUuV0xpHS16YwBhseuuBjYjoolFcR20Ibaa05AMiXtGS/sHD Lm5nq949RlYsmVZpeC9HxQW/H8dWg4URNvUfOfKdUlCHnkxeoX/IcQjlO6BmsqdsSYcV 0DtjAY+QxLy9bdo9ivDeEFyJexZOMo9Q3OiD6jqDV1IfEI7AluKMKEh3cWnIkUHjixxz EWnUZ9DZuBhhWjV8dojDTCwd4AFEY+iiVtED0D2whuBz/40e1QoxVQ4CymTdVG3lRgP7 eVWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=jFycCzBUY2ndD2OB9cK6rohJ6DSuRX1OY1L3NUKQzi0=; b=q2jE2i++JZNsAbPPrd8vPfHrUIVY2GXcrf+s/VNULjQqMe3+WueqynjN4RnsYWsmYh OdZZ9vkS+lSRSUtgp1RmcqvZoH8sAnemBwihuI949HXpZv5SbyQZZKH80L4ezY5mk+yt dNTTiRdaPh00+QOJIc3yNLW9d26c7a3oHrEG8S/+9YL/CJUc89SJjr/1FT1t039oHpUY X7rN45huF6QEoeRCbobdoemQWMltPdBhuRFIxi+iF0HL+8e+r3JUsZ2HX0Uy71TokYIC 4fGrZjH79+08VohhSwzFpcFbszytWIRayLwx/eoqA5Kq1uCoz3eXteV12SaDUjp7RwpA iCUA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=OFGzCFKL; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d9si9513165edb.371.2019.09.09.08.06.28; Mon, 09 Sep 2019 08:06:53 -0700 (PDT) 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; dkim=pass header.i=@kernel.org header.s=default header.b=OFGzCFKL; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389383AbfIIIit (ORCPT + 99 others); Mon, 9 Sep 2019 04:38:49 -0400 Received: from mail.kernel.org ([198.145.29.99]:39632 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725818AbfIIIis (ORCPT ); Mon, 9 Sep 2019 04:38:48 -0400 Received: from localhost (unknown [148.69.85.38]) (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 AE91A218AC; Mon, 9 Sep 2019 08:38:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1568018327; bh=h/O/BE7OIazqYv1sKFu2+r3tD8HYU7J0+05Vtn7XDSA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=OFGzCFKLEGpb4HSYK7wqOjse7xpWIrMhPEeXkD5UJUY6rQOqD7XLteS5Im/EzHQxL e9GQlHSK5V9bmKh5ynGYZamrLck/aUUIv76XKXs4wBfzqiL9FMDLu1SHl/N4f91KXP 0n2+vYDxFLZ4jTvOpTdl5sJC9YQs1DcPE3mplFl0= Date: Mon, 9 Sep 2019 09:38:44 +0100 From: Jaegeuk Kim To: Chao Yu Cc: g@jaegeuk-macbookpro.roam.corp.google.com, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: avoid infinite GC loop due to stale atomic files Message-ID: <20190909083844.GC25724@jaegeuk-macbookpro.roam.corp.google.com> References: <20190909012532.20454-1-jaegeuk@kernel.org> <20190909012532.20454-2-jaegeuk@kernel.org> <20190909073011.GA21625@jaegeuk-macbookpro.roam.corp.google.com> <5a473076-14b8-768a-62ac-f686e850d5a6@huawei.com> <20190909080108.GC21625@jaegeuk-macbookpro.roam.corp.google.com> <20190909082112.GA25724@jaegeuk-macbookpro.roam.corp.google.com> <2f5b844c-f722-6a80-a4ab-61bdd72b8be4@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2f5b844c-f722-6a80-a4ab-61bdd72b8be4@huawei.com> User-Agent: Mutt/1.8.2 (2017-04-18) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/09, Chao Yu wrote: > On 2019/9/9 16:21, Jaegeuk Kim wrote: > > On 09/09, Chao Yu wrote: > >> On 2019/9/9 16:01, Jaegeuk Kim wrote: > >>> On 09/09, Chao Yu wrote: > >>>> On 2019/9/9 15:30, Jaegeuk Kim wrote: > >>>>> On 09/09, Chao Yu wrote: > >>>>>> On 2019/9/9 9:25, Jaegeuk Kim wrote: > >>>>>>> If committing atomic pages is failed when doing f2fs_do_sync_file(), we can > >>>>>>> get commited pages but atomic_file being still set like: > >>>>>>> > >>>>>>> - inmem: 0, atomic IO: 4 (Max. 10), volatile IO: 0 (Max. 0) > >>>>>>> > >>>>>>> If GC selects this block, we can get an infinite loop like this: > >>>>>>> > >>>>>>> f2fs_submit_page_bio: dev = (253,7), ino = 2, page_index = 0x2359a8, oldaddr = 0x2359a8, newaddr = 0x2359a8, rw = READ(), type = COLD_DATA > >>>>>>> f2fs_submit_read_bio: dev = (253,7)/(253,7), rw = READ(), DATA, sector = 18533696, size = 4096 > >>>>>>> f2fs_get_victim: dev = (253,7), type = No TYPE, policy = (Foreground GC, LFS-mode, Greedy), victim = 4355, cost = 1, ofs_unit = 1, pre_victim_secno = 4355, prefree = 0, free = 234 > >>>>>>> f2fs_iget: dev = (253,7), ino = 6247, pino = 5845, i_mode = 0x81b0, i_size = 319488, i_nlink = 1, i_blocks = 624, i_advise = 0x2c > >>>>>>> f2fs_submit_page_bio: dev = (253,7), ino = 2, page_index = 0x2359a8, oldaddr = 0x2359a8, newaddr = 0x2359a8, rw = READ(), type = COLD_DATA > >>>>>>> f2fs_submit_read_bio: dev = (253,7)/(253,7), rw = READ(), DATA, sector = 18533696, size = 4096 > >>>>>>> f2fs_get_victim: dev = (253,7), type = No TYPE, policy = (Foreground GC, LFS-mode, Greedy), victim = 4355, cost = 1, ofs_unit = 1, pre_victim_secno = 4355, prefree = 0, free = 234 > >>>>>>> f2fs_iget: dev = (253,7), ino = 6247, pino = 5845, i_mode = 0x81b0, i_size = 319488, i_nlink = 1, i_blocks = 624, i_advise = 0x2c > >>>>>>> > >>>>>>> In that moment, we can observe: > >>>>>>> > >>>>>>> [Before] > >>>>>>> Try to move 5084219 blocks (BG: 384508) > >>>>>>> - data blocks : 4962373 (274483) > >>>>>>> - node blocks : 121846 (110025) > >>>>>>> Skipped : atomic write 4534686 (10) > >>>>>>> > >>>>>>> [After] > >>>>>>> Try to move 5088973 blocks (BG: 384508) > >>>>>>> - data blocks : 4967127 (274483) > >>>>>>> - node blocks : 121846 (110025) > >>>>>>> Skipped : atomic write 4539440 (10) > >>>>>>> > >>>>>>> Signed-off-by: Jaegeuk Kim > >>>>>>> --- > >>>>>>> fs/f2fs/file.c | 10 +++++----- > >>>>>>> 1 file changed, 5 insertions(+), 5 deletions(-) > >>>>>>> > >>>>>>> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c > >>>>>>> index 7ae2f3bd8c2f..68b6da734e5f 100644 > >>>>>>> --- a/fs/f2fs/file.c > >>>>>>> +++ b/fs/f2fs/file.c > >>>>>>> @@ -1997,11 +1997,11 @@ static int f2fs_ioc_commit_atomic_write(struct file *filp) > >>>>>>> goto err_out; > >>>>>>> > >>>>>>> ret = f2fs_do_sync_file(filp, 0, LLONG_MAX, 0, true); > >>>>>>> - if (!ret) { > >>>>>>> - clear_inode_flag(inode, FI_ATOMIC_FILE); > >>>>>>> - F2FS_I(inode)->i_gc_failures[GC_FAILURE_ATOMIC] = 0; > >>>>>>> - stat_dec_atomic_write(inode); > >>>>>>> - } > >>>>>>> + > >>>>>>> + /* doesn't need to check error */ > >>>>>>> + clear_inode_flag(inode, FI_ATOMIC_FILE); > >>>>>>> + F2FS_I(inode)->i_gc_failures[GC_FAILURE_ATOMIC] = 0; > >>>>>>> + stat_dec_atomic_write(inode); > >>>>>> > >>>>>> If there are still valid atomic write pages linked in .inmem_pages, it may cause > >>>>>> memory leak when we just clear FI_ATOMIC_FILE flag. > >>>>> > >>>>> f2fs_commit_inmem_pages() should have flushed them. > >>>> > >>>> Oh, we failed to flush its nodes. > >>>> > >>>> However we won't clear such info if we failed to flush inmen pages, it looks > >>>> inconsistent. > >>>> > >>>> Any interface needed to drop inmem pages or clear ATOMIC_FILE flag in that two > >>>> error path? I'm not very clear how sqlite handle such error. > >>> > >>> f2fs_drop_inmem_pages() did that, but not in this case. > >> > >> What I mean is, for any error returned from atomic_commit() interface, should > >> userspace application handle it with consistent way, like trigger > >> f2fs_drop_inmem_pages(), so we don't need to handle it inside atomic_commit(). > > > > f2fs_ioc_abort_volatile_write() will be triggered. > > If userspace can do this, we can get rid of this patch, or am I missing sth? We don't know when that will come. And, other threads are waiting for GC here. > > - f2fs_ioc_abort_volatile_write > - f2fs_drop_inmem_pages > - clear_inode_flag(inode, FI_ATOMIC_FILE); > - fi->i_gc_failures[GC_FAILURE_ATOMIC] = 0; > - stat_dec_atomic_write(inode); > > > > >> > >>> > >>>> > >>>> Thanks, > >>>> > >>>>> > >>>>>> > >>>>>> So my question is why below logic didn't handle such condition well? > >>>>>> > >>>>>> f2fs_gc() > >>>>>> > >>>>>> if (has_not_enough_free_secs(sbi, sec_freed, 0)) { > >>>>>> if (skipped_round <= MAX_SKIP_GC_COUNT || > >>>>>> skipped_round * 2 < round) { > >>>>>> segno = NULL_SEGNO; > >>>>>> goto gc_more; > >>>>>> } > >>>>>> > >>>>>> if (first_skipped < last_skipped && > >>>>>> (last_skipped - first_skipped) > > >>>>>> sbi->skipped_gc_rwsem) { > >>>>>> f2fs_drop_inmem_pages_all(sbi, true); > >>>>> > >>>>> This is doing nothing, since f2fs_commit_inmem_pages() removed the inode > >>>>> from inmem list. > >>>>> > >>>>>> segno = NULL_SEGNO; > >>>>>> goto gc_more; > >>>>>> } > >>>>>> if (gc_type == FG_GC && !is_sbi_flag_set(sbi, SBI_CP_DISABLED)) > >>>>>> ret = f2fs_write_checkpoint(sbi, &cpc); > >>>>>> } > >>>>>> > >>>>>>> } else { > >>>>>>> ret = f2fs_do_sync_file(filp, 0, LLONG_MAX, 1, false); > >>>>>>> } > >>>>>>> > >>>>> . > >>>>> > >>> . > >>> > > . > >